ox-tools / cargo-coverage-gate
AGENTS.md28 starsChanged 11 days agoMITView on GitHub
Inherits everything from the workspace-root AGENTS.md. Additions below are specific to this crate. cargo-gamma runs in CI against this crate. Before claiming a change is done, prefer adding direct unit tests for any private helper whose arithmetic, comparisons, or branch conditions would otherwise only be exercised through wider integration tests — those are the mutants the runner catches most often, and surviving mutants block the build. Keep gamma::skip comment suppressions narrow: identify the specific mutation kinds and include a reason.…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- crates/cargo-anvil/AGENTS.mdAGENTS.md
- cargo-anvil-adoptionSkill
- cargo-anvil-adoptionSkill
- code-reviewSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Keep gamma::skip comment suppressions narrow: identify the specific mutation kinds and include a reason.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
cargo-coverage-gate — AI Agents Guidelines
Inherits everything from the workspace-root AGENTS.md. Additions below
are specific to this crate.
Mutation Testing
cargo-gamma runs in CI against this crate. Before claiming a change
is done, prefer adding direct unit tests for any private helper whose
arithmetic, comparisons, or branch conditions would otherwise only be
exercised through wider integration tests — those are the mutants the
runner catches most often, and surviving mutants block the build.
Keep gamma::skip comment suppressions narrow: identify the specific
mutation kinds and include a reason. Reserve them for equivalent
mutants or native boundaries that cannot be exercised in-process.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.