guided-review
Skill0 starsChanged 15 days agoNo licenceView on GitHub
Guide the user through reviewing a commit, a range of commits, a branch, uncommitted changes or a pull request, so they read every change in a sensible order and see the problems in it. Works out what the change does from the code, maps every hunk into units ranked by importance, accounts for every branch of the changed logic, and reviews each unit for bugs, flawed logic, readability, cleanliness and logging (levels, audit, debugging), verifying every finding against the code. Then lists the important changes and walks the user through them one stop at a time - what changed, where to read, every branch, and the findings there - recording the user's verdicts. Use when the user wants to go through, walk through or read through a commit, diff, branch or PR with help, wants a guided or interactive review, asks what the important changes are, or invokes /guided-review with a commit, range, branch, PR number or URL (options --doc, --by-commit, --thorough, --models). Read-only; posts nothing unless asked.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- plannotator/guidestheir own version, first seen Nov 1, 2026
- slopus/happy-desktoptheir own version, first seen Nov 1, 2026
- LizAndCollie/skillstheir own version, first seen Sep 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
- slopus/happy-desktop★ 106same name
- plannotator/guides★ 34same name
- LizAndCollie/skills★ 2same 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.
- conventionsSkill
- deep-reviewSkill
- dep-hygieneSkill
- deslopSkill
- error-pathsSkill
- hotspotsSkill
- perf-passSkill
- pr-reviewSkill
- sdlc-fast-piSkill
- sdlc-fastSkill
- sdlc-loopSkill
- test-strengthSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
1
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.