dvm-cli
AGENTS.md0 starsChanged 34 days agoApache-2.0View on GitHub
Instructions for coding agents working in this repository. Load .agents/skills/public-readme/SKILL.md before changing README.md or a root community file. For test changes and test-value audits, follow the test-audit skill. Keep a comment when it records a reason, constraint, unit, lifecycle or compatibility promise, or API behavior that the code does not make clear. Remove narration, stale history, review provenance, and boilerplate. Exported or public symbols do not require JSDoc. Retain functional JSDoc types, directives, licenses, error codes, and machine-output contracts. Tests…
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 32,671 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 repository3 other files it gives its agents.
- public-readmeSkill
- test-auditSkill
- dvmSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Keep a comment when it records a reason, constraint, unit, lifecycle or compatibility promise, or API behavior that the code does not make …
- Distinctive: line 11
Remove narration, stale history, review provenance, and boilerplate.
- Distinctive: line 19
No tautological tests: Do not assert a fixture against itself, verify only the configured output of a mock, or calculate an expected value …
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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
Instructions for coding agents working in this repository.
Load .agents/skills/public-readme/SKILL.md before changing README.md or a root community file.
Comments and tests
For test changes and test-value audits, follow the test-audit skill.
Keep a comment when it records a reason, constraint, unit, lifecycle or compatibility promise, or API behavior that the code does not make clear. Remove narration, stale history, review provenance, and boilerplate. Exported or public symbols do not require JSDoc. Retain functional JSDoc types, directives, licenses, error codes, and machine-output contracts.
Tests must exercise a production behavior that can fail or an independently specified contract. Use the cheapest meaningful boundary and mock external dependencies, not the behavior under test.
No tautological tests. Do not assert a fixture against itself, verify only the configured output of a mock, or calculate an expected value with the same implementation under test. Before removing or combining a test, map each distinct failure to retained coverage, or explain why it protects no meaningful contract. Keep source guards when the source property is the contract, with a negative control that the guard rejects.
Independently specified round-trip, idempotence, retry/replay, and metamorphic properties are valid when a production defect can violate them. Preserve distinct money, recovery, lifecycle, and release checks. Do not add a new test solely because prose or a comment changed; existing required gates still apply. A claim that a runtime failure cannot happen needs a test that reaches that failure, or narrower wording. Do not use a deletion quota.
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.

