Rust Doc Sweep
SkillDocs & knowledgeComprehensive public-api quality pass over the core crates, reducing pub visibility and documenting every public item to a deny(missing_docs) standard. Use for crate-wide documentation or visibility sweeps.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Rust Doc Sweep skill
What this skill tells your AI
The instructions your AI receives, as published by mrchantey/beet in .agents/skills/docs-rust-sweep/SKILL.md and read by ahel’s review.
Task
We will now do a comprehensive code quality pass for the core crates of this project.
This task has the primary goal of improving public apis:
- Reduce usage of
pub: preferpub(super),pub(crate)etc wherever it makes sense, this includes at the module level and for struct fields. - Public Docs: ensure all public apis are well documented according to RFC 1574, except where it would be overly verbose.
While we are passing through source files we should also consider two secondary goals: 3. Comments: ensure all complex logic explains well its behavior 4. Tests: ensure all tests are of high quality 5. Integration tests and examples: these should also be well documented. examples should be in root directory, not individual crates.
Conventions
- QUALITY NOT QUANTITY: LLMs love writing text, but if its overly verbose or explaining the obvious, this has a negative value. Ensure only whats needed is used, ie
MyStruct::newusually does not need an example, just a one-liner doc. General usage should be in the top levelMyStructdocs - Many modules will need module-level documentation. try not to duplicate struct docs in the module level. The module level should contain very high level concepts and most modules dont need examples.
- Do not discard comments, todos unless certain they are no longer relevant
Process
For each crate do the following:
- add
#![deny(missing_docs)] - add docs until
cargo checkpasses with all features, both native and wasm:cargo check -p beet_core --all-featurescargo check -p beet_core --all-features --target wasm32-unknown-unknown
- Run doc tests with all features:
timeout 1m cargo test -p beet_core --doc --all-features | tail 30
- mark the crate as done in the checklist below
Crates
List the workspace crates (ls crates/) here in dependency order at the start of a sweep, basic dependencies first, and check them off as they complete. Skip those marked completed. Do not ask to continue to the next one, just do it.
Finally verify all changes by running: just test-all
Signals
- GitHub stars
- 134
- Forks
- 8
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
docs-rust-sweep- Source
- github.com/mrchantey/beet