review-behaviors
Skill125 starsChanged 13 days agoApache-2.0View on GitHub
Reviews the quality and coherence of behavior statements. Use when reviewing behavior changes in a diff, checking a new or edited behavior statement, or auditing the behavior statements of a codebase.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- fluentSkill
- review-architectureSkill
- review-documentationSkill
- review-skillsSkill
- review-testsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read references/behaviors.md for behavior-writing standards.
- Very specific: line 19
Verify it uses one of the six EARS patterns from references/behaviors.md.
- Very specific: line 23
Check the collection for coherence — vocabulary consistency, contradictions, coverage, and redundancy — using the "Coherence across …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Purpose
Decide whether the behavior statements under review are fit to ship. Identify improvements that would make each statement more precise about what the system does, or the collection more coherent and complete as a whole.
Scope
The invoking layer decides what's in scope. For a diff-scoped review, that's the behavior statements changed in the diff. For a full-codebase audit, that's the entire set of behavior statements. Check each statement for quality and check the collection for coherence and completeness.
Method
- Read
references/behaviors.mdfor behavior-writing standards. - For each in-scope behavior statement:
- Verify it uses one of the six EARS patterns from
references/behaviors.md. Statements without a recognized trigger (WHEN, WHILE, IF, WHERE) or without "THE SYSTEM SHALL" are hard to verify. - Evaluate against the "Properties of a good behavior statement" and "What not to specify" sections in
references/behaviors.md. - Identify improvements.
- Verify it uses one of the six EARS patterns from
- Check the collection for coherence — vocabulary consistency, contradictions, coverage, and redundancy — using the "Coherence across behavior statements" section of
references/behaviors.md. - For each improvement, decide if it blocks shipping. Statements that leak implementation, combine multiple behaviors, or lack a way to verify typically block. Style issues and minor phrasing don't.
The invoking layer may add checks in addition to those above.
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.