review-all
Skill2 starsChanged 12 days agoMITView on GitHub
Run code-review, ponytail-review and (when the diff crosses a trust boundary) security-review on one diff, in one command.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- daryaKuto/claude-skillstheir own version, first seen Nov 15, 2026
- unlockers-ai/unlockers-skills-librarytheir own version, first seen Nov 8, 2026
- NovruzAliyevDev/skillstheir own version, first seen Nov 1, 2026
- paultyng/skill-issuetheir own version, first seen Oct 13, 2026
- jtenniswood/espcontroltheir own version, first seen Oct 8, 2026
- ncoevoet/claude-review-alltheir own version, first seen May 28, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- jtenniswood/espcontrol★ 1.2ksame name
- ncoevoet/claude-review-all★ 45same name
- paultyng/skill-issue★ 8same name
- NovruzAliyevDev/skills★ 4same name
- unlockers-ai/unlockers-skills-library★ 4same name
- clinton3141/dotcopilot★ 0same name
- daryaKuto/claude-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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- guidelines/claude.mdCLAUDE.md
- chat-idSkill
- codewalkSkill
- compassSkill
- corkboardSkill
- keystone-reactSkill
- keystoneSkill
- oracleSkill
- playbookSkill
- scribeSkill
- skillsmithSkill
- ticketsmithSkill
- watermarkSkill
- workbookSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run the review skills below on one shared diff and report each one's findings.
- Distinctive: line 26
Done when: every reviewer has returned a report or a recorded skip.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Run the review skills below on one shared diff and report each one's findings. This is review only. Leave the code untouched.
1. Pin the diff
- Fixed point: the argument, else the default branch (
main). - Diff command:
git diff $(git merge-base <fixed point> HEAD). It compares the merge-base to the working tree, so uncommitted work counts. Pass this exact command to every reviewer in place of its own default. - Spec: the repo's plan file (
PLAN.md, or the spec the commits name), if one exists.
Done when: the fixed point resolves, the diff is non-empty, and you hold the diff command, git diff --stat and the spec path.
2. Run the reviewers
Invoke each with the Skill tool, one after another, giving each the diff command:
code-review: pass the fixed point and the spec path.ponytail:ponytail-review.security-review: only when the diff touches a trust boundary: auth or sign-in, secrets or tokens, permissions or tool gates, or input from outside (web pages, chat messages, HTTP requests, tool results, files the user uploads). Otherwise record "skipped: no trust boundary in the diff" and the files you checked.
Done when: every reviewer has returned a report or a recorded skip.
3. Report
One ## heading per reviewer, its findings as it gave them. Keep the reviewers separate: a finding two reviewers raised stays under both, marked "(also in X)". End with one line per reviewer naming its worst finding, then the offer: "Apply the fixes? I'll use receiving-code-review if it is installed."
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.

