team-code-review
Skill11 starsChanged 3 months agoMITView on GitHub
Use for running the Team code review phase only on explicit request. Never infer from a plain review request. Reviews and fixes the branch.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Shehabov/ai-dev-crewtheir own version, first seen Sep 30, 2026
- devfullcycle/mba-ia-labs-skillstheir own version, first seen Jul 16, 2026
- dgalarza/agent-skillstheir own version, first seen May 21, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- dgalarza/agent-skills★ 72same name
- devfullcycle/mba-ia-labs-skills★ 7same name
- Shehabov/ai-dev-crew★ 4same 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
- create-team-skillSkill
- version-bumpSkill
- team-designSkill
- team-fixSkill
- team-implementSkill
- team-migrateSkill
- team-planSkill
- team-prSkill
- team-questionSkill
- team-researchSkill
- team-security-reviewSkill
- teamSkill
- team-structureSkill
- team-updateSkill
- team-worktreeSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Before each dispatch or retry, read host dispatch and supply its resolved installed paths.
- Distinctive: line 11
Before artifact work, read artifact schema.
- Distinctive: line 12
Before the tier sort, read finding format.
- Distinctive: line 13
Before each consuming step, read its linked shared rules from this installed skill directory.
- Distinctive: line 14
If a required read fails, stop that step with the exact path.
- Distinctive: line 15
Before finalizing prose you author, read the writing standards.
- Very specific: line 20
Write one review-<n>.md per completed round.
- Distinctive: line 21
Never: ask the user which Blocking or Major items to address (the no-consult rule).
- Distinctive: line 26
Read each reference completely when reaching it, in order.
- Distinctive: line 33
Read and apply: execution rules.
“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.
Files
Team Code Review
Before each dispatch or retry, read host dispatch and supply its resolved installed paths. Before artifact work, read artifact schema. Before the tier sort, read finding format. Before each consuming step, read its linked shared rules from this installed skill directory. If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading. Before finalizing prose you author, read the writing standards. Relay completed reviewer reports unchanged.
Core contracts
- Require
1-task.md, a non-default branch, at least one commit beyond the merge-base, and a tree clean outsidedocs/plans/; in multi-repo mode, every worktree4-repos.mdlists. - Write one
review-<n>.mdper completed round; never overwrite a record. - Never ask the user which Blocking or Major items to address (the no-consult rule). The loop has no count cap; it ends only when no Blocking or Major finding remains.
- At PASS, return to the
/teamphase loop in the same turn when the TodoWrite ledger holds aPRphase item; otherwise print the Next line for/team-security-review. Never loadteam-security-revieworteam-pr.
Procedure references
Read each reference completely when reaching it, in order.
- Input
- Execution
Applied principles
Read and apply: execution rules.
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.