code-reviewer
Skill8 starsChanged 3 months agoMITView on GitHub
Reviews the current diff (uncommitted or open PR) for bugs, security risks, constitution violations, and divergences from specs. Delegates the review to a clean-context reviewer. Use before relevant commits or when the user asks "review what changed".
182 other projects use a version of this.
Adopted by
Most recently taken up by
- santiago-migoni/claude-skillstheir own version, first seen Nov 8, 2026
- SaehwanPark/agent-skills-archivetheir own version, first seen Nov 8, 2026
- nainishshafi/developer-productivity-skillstheir own version, first seen Nov 8, 2026
- Flowerf19/agents-skillstheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- kazemcodes/skill-treetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use git-doc-updater, git-precommit and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
u9401066Skillgit-doc-updater
Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布.
Also in 5 projects that use this
- u9401066Skill
git-precommit
Orchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送.
Also in 5 projects that use this
JeffallanSkillshopify-expert
Builds and debugs Shopify themes (.liquid files, theme.json, sections), develops custom Shopify apps (shopify.app.toml, OAuth, webhooks), and implements Storefront API integrations for headless storefronts. Use when building or customizing Shopify themes, creating Hydrogen or custom React storefronts, developing Shopify apps, implementing checkout UI extensions or Shopify Functions, optimizing performance, or integrating third-party services. Invoke for Liquid templating, Storefront API, app development, checkout customization, Shopify Plus features, App Bridge, Polaris, or Shopify CLI workflows.
Also in 5 projects that use this
- JeffallanSkill
spec-miner
Reverse-engineering specialist that extracts specifications from existing codebases. Use when working with legacy or undocumented systems, inherited projects, or old codebases with no documentation. Invoke to map code dependencies, generate API documentation from source, identify undocumented business logic, figure out what code does, or create architecture documentation from implementation. Trigger phrases: reverse engineer, old codebase, no docs, no documentation, figure out how this works, inherited project, legacy analysis, code archaeology, undocumented features.
Also in 6 projects that use this
- +4 more from u9401066
- +4 more from Jeffallan
Other versions182 projects use a version of this.
Word for word · 1
- jcarlos78/GAIDE★ 8100% same
Edited · 0
None found.
Wrote their own version · 181
- google-gemini/gemini-cli★ 109ksame name
- NVIDIA/SkillSpector★ 25ksame name
- Jeffallan/claude-skills★ 12ksame name
- jewbetcha/openflight★ 1.2ksame name
- web-infra-dev/rsdoctor★ 1.2ksame name
- zhnnky329/MathModeling-skills★ 1.1ksame name
- MageByte-Zero/spec-superflow★ 875same name
- waybarrios/opencode-power-pack★ 547same name
- Karanjot786/TermUI★ 238same name
- elithrar/dotfiles★ 222same name
171 more not listed
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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- adr-writerSkill
- security-reviewerSkill
- spec-writerSkill
- test-generatorSkill
- verifierSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 154 edited versions we read keep these.
5
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 16
Before commits that affect behavior
- Distinctive: line 17
When the user asks for an explicit review
- Distinctive: line 18
After implementation guided by a spec
- Distinctive: line 19
Before opening a PR
- Distinctive: line 45
Do not pass: summaries of the implementation conversation, justifications for choices made, or hints about which parts you're confident in.
“Common” is measured: kept by at least 6 in 10 of the 154 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
<!-- GENERATED from agents/skills/code-reviewer.md by scripts/sync-adapters.sh — edit the source and re-run; do not edit this file. -->Skill: code-reviewer
Why a clean context
An agent that wrote the code is biased when reviewing it: its context contains the rationalizations that produced the bugs. The review therefore runs in a clean context — a reviewer following the rubric in agents/reviewers/code-reviewer.md that sees only the diff and the governing documents, exactly like a future maintainer would. In Claude Code this is the code-reviewer subagent; in tools without subagents, open a fresh conversation/agent given only the rubric and the brief below. Your job in this skill is orchestration, not judgment.
When to activate
- Before commits that affect behavior
- When the user asks for an explicit review
- After implementation guided by a spec
- Before opening a PR
Playbook
1. Identify the review scope
git diff --staged # if anything is staged
git diff # otherwise, working treeFor an open PR, use gh pr diff <number>.
2. Locate the governing documents
specs/constitution.md- The feature's
specs/<feature>/spec.mdandplan.md(the plan carries the sprint contract) - Relevant ADRs in
docs/adr/
3. Spawn the reviewer with a minimal brief
Launch the clean-context reviewer (the code-reviewer subagent in Claude Code; elsewhere, a fresh conversation pointed at agents/reviewers/code-reviewer.md). Pass only:
- How to collect the diff (the exact command from step 1)
- The document paths from step 2
Do not pass: summaries of the implementation conversation, justifications for choices made, or hints about which parts you're confident in. If the reviewer needs author context to understand the code, that's a finding, not a gap to pre-fill.
4. Deliver the report
Present the subagent's report to the human verbatim — do not soften blockers, do not pre-answer findings. The human decides what to fix, dismiss, or justify.
Expected output
The subagent's structured Markdown report. Do not commit nor apply changes — this flow is read-only and advisory.
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.