local-code-review
Skill8 starsChanged 7 days agoApache-2.0View on GitHub
Review local Git changes and return evidence-backed P0/P1/P2 code-review findings.
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
- derailed-dash/dazbo-agent-skillstheir own version, first seen Nov 1, 2026
- rdlugs/ai-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
- aditya-deokar/software-factory★ 0same name
- rdlugs/ai-skills★ 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- github-pr-reviewSkill
- review-backendSkill
- review-coreSkill
- review-deep-investigationSkill
- review-frontendSkill
- review-publish-githubSkill
- review-requirementsSkill
- review-runtime-checkSkill
- review-securitySkill
- review-suggestionsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
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 12
When the user asks to review local changes, run review-core on the local change and return its report.
“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.
Files
local-code-review
Compatibility entrypoint for the v2 name. It reviews local Git changes by
delegating to review-core.
When the user asks to review local changes, run review-core on the local
change and return its report. Everything else — scope, severity, evidence,
the decision and the safety guarantees — is review-core's and is not
restated here.
Requires review-core. If it is not installed, stop and ask the user to
install it (review-core is invocable directly, with the same result).
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.