About repo-review
A skill for reviewing a current worktree or a fixed, verified code snapshot. It routes reviews to applicable checklists and standards, keeps evidence tied to the selected basis, and reports findings with scope and verification gaps.
Key features
- 01Worktree and fixed-basis review paths
- 02Conditional standards and reference routing
- 03Basis-specific evidence handling
- 04P0–P3 findings and observations
Use cases
- 01Reviewing changes in the current worktree
- 02Assessing a commit or verified review package
- 03Checking applicable UI, protocol, or performance concerns
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/repo-reviewin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlassets/frontend-visual-evidence.schema.jsonreferences/checklist.mdcode-quality.mdcodebase-design.mddocumentation-authority-review.mdeval-cases.mdfrontend-css-governance.mdfrontend-performance-review.mdfrontend-visual-evidence.mdinteraction-motion-review.mdopenapi-contract-governance.mdproject-grounding.mdprotocol-contracts.mdreview-integration.mdstandards-and-spec.mdui-components-and-tokens.mdusage.mdworktree-checklist.mdworktree-examples.mdscripts/validate-frontend-visual-evidence.pyDetails
From the project READMERepository Review
Entry Gate
Review one current Worktree or one immutable range/snapshot/review package. Freeze the selected basis before conclusions; preserve read-only authority and stop when it or its required objects cannot be verified.
Route Map
| Request condition | Read | Result |
|---|---|---|
| Immutable commit/range/snapshot or verified review package | fixed-basis checklist and Standards/Spec | Fixed-basis P0-P3 findings/observations |
| Current Worktree review | worktree checklist and Standards/Spec | Worktree P0-P3 findings/observations |
| Product/UI/DESIGN/map authority changes apply | documentation authority | Authority closure review |
| Frontend visual/layout/interaction/motion change applies | visual evidence, CSS governance, components/tokens, and/or motion review | Conditional visual review |
| Frontend loading, responsiveness, rendering, memory, request, cache or activation change | performance regression boundaries | Qualified shared-effect and business-regression findings |
| OpenAPI/protocol, cross-boundary, or external provider evidence applies | protocol contracts, OpenAPI governance, project grounding, and/or review integration | Qualified evidence integration |
| Design/quality or Worktree example is needed | codebase design and/or worktree examples | Bounded analysis |
Invariants
- Do not mix evidence between bases; current content does not prove another SHA.
- A review package, graph, test, or provider output is evidence only after basis verification.
- Findings require concrete reachability/impact and exact owner; do not mutate source or Git.
Output Map
Return basis/scope, standards and spec disposition, findings/observations, evidence,
checks, exclusions, and Not verified gaps.
Reference Map
- Read fixed-basis checklist for immutable commit/range/snapshot or verified-package review; read worktree checklist for current Worktree review. Do not combine their basis acquisition rules.
- Read Standards/Spec for every review.
- Load each conditional reference named in the Route Map only when its condition applies, including code quality for maintainability findings.
- Read usage for review modes and boundaries.
- Maintainers only: read eval cases; do not load it during ordinary runtime.
Comments
Markdown supported