pre-commit-review
Skill1 starsChanged 7 months agoNo licenceView on GitHub
Perform a deep, senior-engineer code review on uncommitted local git changes before the user commits. This is a THOROUGH review: not just code quality, but whether the code actually does what it set out to do, and whether it is covered by real tests (not just happy-path tests). Trigger whenever the user says "review my code", "pre-commit review", "check my changes", "review uncommitted code", "review before commit", "look at my diff", "what do you think of my changes", "is this ready to commit?", "give me a review", or any variation. If the user points at a requirements.md / spec or briefly says what the change is meant to do, review the code AGAINST that intent; otherwise do a general review and infer intent from the diff. The deliverable is a visual HTML Artifact (score, charts, diagrams, code snippets) — never a wall-of-text markdown file. Always follow this skill's full workflow — do not just run git diff yourself.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- moberghr/mtk-agent-toolkittheir own version, first seen Oct 25, 2026
- shsha4/claude-skillstheir own version, first seen Aug 19, 2026
- System-Error-Worldwide/the-looptheir own version, first seen Aug 17, 2026
- felipeArnold/filament-ai-skillstheir own version, first seen Jun 13, 2026
- liuhean2021/anan-agent-skillstheir own version, first seen Apr 11, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- felipeArnold/filament-ai-skills★ 9same name
- moberghr/mtk-agent-toolkit★ 9same name
- liuhean2021/anan-agent-skills★ 1same name
- shsha4/claude-skills★ 1same name
- System-Error-Worldwide/the-loop★ 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 repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-new-featureSkill
- debugging-wizardSkill
- eli5Skill
- generate-service-documentationSkill
- grill-meSkill
- new-go-serviceSkill
- review-codebaseSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 13 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
3
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 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.
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.