resilientmindset01-commitsresilientmindset01-commits/claude-code-skills-free/skills/review-ai-code/SKILL.mdreview-ai-code
Skill0 starsChanged 44 days agoNo licenceView on GitHub
Review AI-generated code the way a senior developer does -- catch the bugs that pass the tests but are not safe to ship. Use when Claude (or any model) has written a feature, endpoint or module and you are about to merge it, or when you are reviewing a large AI-written pull request. Walks an ordered 9-step review (requirement -> decisions -> logic -> assumptions -> security -> performance -> overengineering -> error handling -> maintainability) plus a pre-merge checklist. The model writes the code; you decide what is safe to ship -- only one of those jobs got automated. Also covers what to do when the diff outgrows the reviewer: reviewing an intent artifact and interrogating the code instead of reading every line, the three conditions that make that honest, and why you never approve the explanation in place of the change.
- Reads credentials
In this repository4 other files it gives its agents.
- llms.txtllms.txt
- claude-md-rulesSkill
- context-curationSkill
- session-handoff-memorySkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
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 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.