code-review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- code-review
- description
- Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
02 资源文件 3
- 参考文档agents/openai.yaml100 B
- 参考文档CREDITS.md2.6 KB
- 脚本ownership-facts.mjs4.2 KB
03 SKILL.md 正文
A prompt or brief naming this skill is its invocation.
Two-axis review of the diff between HEAD and a fixed point the user supplies:
- Standards: does the code conform to this repo's documented coding standards?
- Spec: does the code faithfully implement the originating issue / spec?
Both axes run as parallel sub-agents so they don't pollute each other's context, then this skill aggregates their findings.
The issue tracker should have been provided to you.
Process
1. Pin the fixed point
Whatever the user said is the fixed point (a commit SHA, branch name, tag, main, HEAD~5, etc.). If they didn't specify one, ask for it.
Resolve the fixed point and HEAD to full commit SHAs with
git rev-parse --verify <ref>^{commit}, then pin their merge-base with
git merge-base <fixed-point-sha> <head-sha>. Capture the diff command once:
git diff <comparison-base-sha> <head-sha>. Also note the commits via
git log <fixed-point-sha>..<head-sha> --oneline. Keep these SHAs for the
facts and both axes even if a branch moves.
Before going further, confirm both refs resolve and the diff is non-empty. A bad ref or empty diff should fail here, not inside two parallel sub-agents.
2. Identify the spec source
Look for the originating spec, in this order:
- Issue references in the commit messages (
#123,Closes #45, GitLab!67, etc.), fetched via the workflow indocs/agents/issue-tracker.md. The spec is the issue's implementation contract; read the validator’s selected source/revision and the tracker’s mode rules. Prepared mode retains latest-brief comments; active body mode permits only the exact unchanged inventoried legacy exception until migration. Review the selected contract and treat other discussion as context; comments cannot supersede a migrated body. - A path the user passed as an argument.
- A spec file under
docs/,specs/, or.scratch/matching the branch name or feature. - If nothing is found, ask the user where the spec is. If they say there isn't one, the Spec sub-agent will skip and report "no spec available".
3. Identify the standards sources
Anything in the repo that documents how code should be written, such as CODING_STANDARDS.md or CONTRIBUTING.md.
On top of whatever the repo documents, the Standards axis always carries the smell baseline below: a fixed set of Fowler code smells (Refactoring, ch.3) that applies even when a repo documents nothing. Two rules bind it:
- The repo overrides. A documented repo standard always wins; where it endorses something the baseline would flag, suppress the smell.
- Always a judgement call. Each smell is a labelled heuristic ("possible Feature Envy"), never a hard violation. Like any standard here, skip anything tooling already enforces.
Each smell reads what it is → how to fix; match it against the diff:
- Mysterious Name: a function, variable, or type whose name doesn't reveal what it does or holds. → rename it; if no honest name comes, the design's murky.
- Duplicated Code: the same logic shape appears in more than one hunk or file in the change. → extract the shared shape, call it from both.
- Feature Envy: a method that reaches into another object's data more than its own. → move the method onto the data it envies.
- Data Clumps: the same few fields or params keep travelling together (a type wanting to be born). → bundle them into one type, pass that.
- Primitive Obsession: a primitive or string standing in for a domain concept that deserves its own type. → give the concept its own small type.
- Repeated Switches: the same
switch/if-cascade on the same type recurs across the change. → replace with polymorphism, or one map both sites share. - Shotgun Surgery: one logical change forces scattered edits across many files in the diff. → gather what changes together into one module.
- Divergent Change: one file or module is edited for several unrelated reasons. → split so each module changes for one reason.
- Speculative Generality: abstraction, parameters, or hooks added for needs the spec doesn't have. → delete it; inline back until a real need shows.
- Message Chains: long
a.b().c().d()navigation the caller shouldn't depend on. → hide the walk behind one method on the first object. - Middle Man: a class or function that mostly just delegates onward. → cut it, call the real target direct.
- Refused Bequest: a subclass or implementer that ignores or overrides most of what it inherits. → drop the inheritance, use composition.
4. Collect ownership facts
Before either axis starts, run the bundled collector from the repository root:
node <this skill's directory>/ownership-facts.mjs <comparison-base-sha> <head-sha>
It needs Node.js and Git with check-attr --source support. It returns a JSON
fact list: touched paths under vendor/ or marked linguist-vendored by
git check-attr in either pinned tree, and added files whose extension or
top-level directory was absent from the comparison base. It uses neither
package-name guesses nor earlier additions in the same diff as the baseline.
An empty list is valid; a failed command must be resolved before review.
These are evidence, not a trigger classifier or an automatic ownership verdict.
Invoke the codebase-design skill and read its Ownership check section.
Pass that section and the fact list to Standards; pass the section to Spec for
its cleanup allowance. If that skill is missing, report the missing dependency
rather than inventing ownership rules.
5. Spawn both sub-agents in parallel
Standards sub-agent prompt should include:
- The full pinned diff command and commit list, plus the fact list from step 4
and
codebase-design's Ownership check section. - The list of standards-source files you found in step 3, plus the smell baseline from step 3 pasted in full (the sub-agent has no other access to it).
- The brief: "Report, per file/hunk where relevant, (a) every place the diff violates a documented standard: cite the standard (file + the rule); and (b) any baseline smell you spot: name it and quote the hunk. Distinguish hard violations from judgement calls: documented-standard breaches can be hard, but baseline smells are always judgement calls, and a documented repo standard overrides the baseline. Skip anything tooling enforces. Apply the Ownership check to the diff using the facts as evidence; distinguish ownership judgment calls from documented violations. Ask whether existing ownership problems in touched code were fixed, noted or filed under that section. Recognize cleanup it permits, listed on its own PR-body line; other out-of-scope defects follow the contribution guide's Findings route. Judge against the recorded contract. Under 400 words."
Spec sub-agent prompt should include:
- The diff command and commit list.
- The path or fetched contents of the spec, the PR body (or proposed body for
work in progress), and
codebase-design's Ownership check section. Give Standards that PR body too, so both can check the listed cleanup. - The brief: "Report: (a) requirements the spec asked for that are missing or partial; (b) behaviour in the diff that wasn't asked for (scope creep); (c) requirements that look implemented but where the implementation looks wrong. Quote the spec line for each finding. Treat cleanup allowed by the Ownership check section and listed on its own PR-body line as permitted, not scope creep. Other out-of-scope defects follow the contribution guide's Findings route. Judge against the recorded contract. Under 400 words."
If the spec is missing, skip the Spec sub-agent and note this in the final report.
6. Aggregate
Present the two reports under ## Standards and ## Spec headings, verbatim or lightly cleaned. Do not merge or rerank findings, because the two axes are deliberately separate (see Why two axes).
End with a one-line summary: total findings per axis, and the worst issue within each axis (if any). Don't pick a single winner across axes: that's the reranking the separation exists to prevent.
Why two axes
A change can pass one axis and fail the other:
- Code that follows every standard but implements the wrong thing → Standards pass, Spec fail.
- Code that does exactly what the issue asked but breaks the project's conventions → Spec pass, Standards fail.
Reporting them separately stops one axis from masking the other.
Reads
Paths are relative to the repository root.
-
docs/agents/issue-tracker.md: how to fetch the issues that commit messages reference, and which comment or body holds an issue's implementation contract. When it is missing and no tracker was provided, look for the spec in step 2's other places, without blocking the review. -
A spec file under
docs/,specs/or.scratch/. When it is missing, ask the user where the spec is, as step 2 says. -
CODING_STANDARDS.md,CONTRIBUTING.mdand anything else in the repository that documents how code should be written. When they are missing, the Standards axis carries only the smell baseline. -
The
codebase-designskill: its Ownership check section supplies the shared rules for both prompts. When it is missing, report the dependency as above. -
vendor/and.gitattributes: the collector reads the pinned trees and Git attributes for evidence. Missing paths or attributes contribute no vendored facts; ordinary diff paths still participate in new-file facts.
04 同仓库更多 Skills
repository-standards
In a project with .repo-standards/, read the repository-wide installed rules and report available CLI and standards updates at the start of any work, including work that changes no file. Look up installed rules before changing a file.
author-standards
Create or revise local Repo Standards from confirmed preferences, including accepted checks, fixes, or ordinary-work author skills, or resume unfinished decisions from authoring notes and the current source.
adopt-repository-standards
Use when the user wants to adopt a standards source or adopt, set up, or apply shared repository conventions or standards in a repository.
review
Review project changes against its documented conventions.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.