local-code-review
Skill0 starsChanged 11 days agoNo licenceView on GitHub
Review uncommitted local code changes (working directory + staged) in a git repo, hunting for bugs, security issues, missing test coverage, and blast radius — everything downstream the change could break — then report findings grouped by severity and lay out an ordered plan to fix them. Use this skill whenever the user asks to review their changes, check their diff, look over what they wrote before committing, sanity-check a patch, trace what a change might affect, or says anything like "review my code", "can you look at this before I push", "did I break anything", "what does this touch", or "check my changes" — even if they don't say the words "code review". Also use it when the user is about to commit, open a PR, or asks whether their work-in-progress looks correct.
- Deletes or force-pushes
3 other projects use a version of this.
Adopted by
Most recently taken up by
- aditya-deokar/software-factorytheir own version, first seen Nov 8, 2026
- amirbena/code-review-skilltheir own version, first seen Nov 5, 2026
- derailed-dash/dazbo-agent-skillstheir own version, first seen Nov 1, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- derailed-dash/dazbo-agent-skills★ 27same name
- amirbena/code-review-skill★ 8same name
- aditya-deokar/software-factory★ 0same name
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 repository9 other files it gives its agents.
- branch-commit-push-prSkill
- git-fix-issueSkill
- git-issueSkill
- grillingSkill
- grill-meSkill
- hermes-reviewSkill
- mr-fixSkill
- mr-reviewSkill
- mr-update-infoSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
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.