do-code-review
Skill1 starsChanged 43 days agoMITView on GitHub
Review the branch you are on since a fixed point, on six Axes (correctness, spec fidelity, repo standards, principles, blast radius, security), every Finding proven to a Rung and written by Bucket into one Review file beside the branch. Use when the user asks to review this branch, review the diff, review since a ref, check the branch before a push, or says 'revisa esse diff', 'revisa essa branch', 'review since main'; also the review step of do. Do not use for a pull request the user wants reviewed and posted on GitHub: that is the bundled /code-review, which this skill leaves untouched.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- saadnvd1/agent-ostheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- saadnvd1/agent-os★ 15same 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 repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- test-authorSkill
- discover-setupSkill
- discoverSkill
- discussSkill
- doSkill
- improve-promptSkill
- journeySkill
- prototypeSkill
- setup-pre-commitSkill
- sketchSkill
- specSkill
- testing-policySkill
- test-triageSkill
- ticketsSkill
The file
Files
Run the do-code-review contract for these arguments, in the mode they name: a fix call reviews nothing, fixes the Review it names and ends with the push command; --no-fix writes the Review and stops, ending with its text and its location; every other call reviews the diff, then fixes and lands, and ends with the Review's text, its location and the push command, or with its outcome alone and the push command when the Gate or a Caller: do line was handed, as only do does.
$ARGUMENTS
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.