review-fix
Skill156 starsChanged 11 days agoMITView on GitHub
Review the requested diff, fix clear correctness issues, and verify the affected behavior.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- davidvornholt/mail-mcptheir own version, first seen Nov 15, 2026
- davidvornholt/mailboxtheir own version, first seen Nov 15, 2026
- raine/skillstheir own version, first seen Nov 1, 2026
- 200iqlabs/shared-skillstheir own version, first seen Oct 31, 2026
- pcode-xyz/simple-skillstheir own version, first seen Oct 20, 2026
- enes-alatas/spooltheir own version, first seen Oct 17, 2026
Used with
Projects with it also use review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- DasDigitaleMomentum/opencode-processing-skills★ 60same name
- enes-alatas/spool★ 48same name
- jhd3197/CachiBot★ 19same name
- EternallLight/tgc-skills★ 11same name
- 200iqlabs/shared-skills★ 4same name
- pcode-xyz/simple-skills★ 4same name
- davidvornholt/mail-mcp★ 2same name
- davidvornholt/mailbox★ 2same name
- raine/skills★ 2same name
- marcuskrogh/skills★ 1same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- check-implSkill
- deploy-workflowSkill
- nwiizo-coding-styleSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
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 10
Read the changed code, callers, and applicable project rules.
- Distinctive: line 29
Run this workflow in the current session unless delegation is explicitly requested.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review staged, unstaged, and relevant untracked changes unless the user selects
a narrower diff. Inspect git status --short and git diff HEAD; if there is
nothing to review, report that and stop.
Read the changed code, callers, and applicable project rules. Prioritize bugs,
security issues, broken references, ignored CLI options, provider capability
mismatches, and violations of the workflow/session/provider boundaries in
AGENTS.md. Use nwiizo-coding-style for Rust structure and duplication analysis;
similarity scores alone do not justify a refactor.
Establish relevant baseline checks when needed to distinguish existing failures from regressions. Fix clear issues within the requested scope with minimal changes. Report design choices and unrelated failures without expanding the assignment. Preserve other contributors' edits; if a fix fails verification, correct it or undo only that fix and report the unresolved finding.
For Rust changes, run the required workspace checks in AGENTS.md, including
tests of affected behavior. For configuration and documentation, validate
syntax, referenced paths, and the affected tool's loading behavior. Reuse passing
checks while their inputs remain unchanged.
Report fixed issues, remaining findings with file references, and verification results. Distinguish pre-existing failures from failures caused by the change. Run this workflow in the current session unless delegation is explicitly requested.
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.

