review
Skill68 starsChanged 4 months agoMITView on GitHub
Universal code review - auto-detects scope from git changes, spec, commit, or brief
192 other projects use a version of this.
Adopted by
Most recently taken up by
- dzhng/skillstheir own version, first seen Nov 15, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- macro-inc/macrotheir own version, first seen Nov 15, 2026
- igoroliveirg/claude-copytheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
Used with
Projects with it also use close-spec, daily-arxiv 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.
dzhngSkillclose-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 5 projects that use this
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
dzhngSkilldesign-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
- +5 more from Lambenthan
- +3 more from dzhng
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- garrytan/gstack★ 142ksame name
- ansible/ansible★ 71ksame name
- docling-project/docling★ 71ksame name
- traefik/traefik★ 66ksame name
- ClickHouse/ClickHouse★ 51ksame name
- temporalio/temporal★ 24ksame name
- ccch1mneyyy/dsh-Go★ 24ksame name
- tisfeng/Easydict★ 15ksame name
- juicedata/juicefs★ 15ksame name
- elie222/inbox-zero★ 13ksame name
182 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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. 0 are common, 21 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 156 edited versions we read keep these.
21
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Use Task tool with these subagent_type values:
- Distinctive: line 70
Read the spec file for context (requirements, architecture, expected behavior)
- Distinctive: line 72
Spec + other source: Use spec as context only, files come from other source
- Very specific: line 85
Use Task(subagent_type="explore-codebase") to find all files related to the feature
- Very specific: line 156
If scope=frontend -> skip all backend agents entirely
- Very specific: line 157
If scope=backend -> skip all frontend agents entirely
- Distinctive: line 158
If no frontend files changed -> skip frontend agents
- Distinctive: line 159
If no backend files changed -> skip backend agents
- Distinctive: line 160
If no files changed at all -> report "No files to review" and stop
- Distinctive: line 171
Aggregate and format the results from section 2 agents: Do NOT re-analyze files yourself.
- Distinctive: line 173
Use the analysis format from checklists/backend-checklist.md and checklists/frontend-checklist.md.
- Distinctive: line 188
Use scoring criteria from checklists.
- Distinctive: line 226
Ask with AskUserQuestion: "Code review complete.
- Distinctive: line 240
After user validation, implement fixes directly using Edit tool.
- Distinctive: line 248
Use Edit tool to apply each fix
- Distinctive: line 254
Do not break existing functionality
- Distinctive: line 255
Do not change business logic unless it's a bug
- Distinctive: line 256
Keep changes minimal but complete
- Distinctive: line 258
If logic seems wrong, ASK before changing
- Distinctive: line 264
Run verification based on scope:
- Distinctive: line 274
Backend and frontend tests are MANDATORY: All existing tests must pass (zero regressions).
- Distinctive: line 282
Use the summary format from templates/review-report.md.
- Distinctive: line 293
FIX WHAT YOU FIND: - after user approval, actually implement fixes with Edit tool
- Very specific: line 295
CHECK i18n: - verify useTranslations (from next-intl) for all frontend text
- Distinctive: line 296
VERIFY BUILDS: - run build commands before completing
“Common” is measured: kept by at least 6 in 10 of the 156 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
YOU ARE EXECUTING THE /review SKILL. The user triggered this skill. Follow ALL instructions below step by step. Do NOT treat this as a freeform conversation - execute the skill workflow.
Think carefully for code review. Follow CLAUDE.md rules.
Critical Instruction
YOU MUST use the Task tool with subagent_type to launch agents. NEVER read or analyze code files directly yourself. Agents do the heavy lifting - you orchestrate and aggregate their results.
Tool Strategy
Use Task tool with these subagent_type values:
explore-docs- Documentation lookupexplore-codebase- Code pattern searchexplore-db- Database schema explorationbackend-code-optimizer- Go code quality analysis (returns score + issues)frontend-code-reviewer- React/TS code quality analysis (returns score + issues)
1. DETERMINE SOURCE & SCOPE
Spec Handling
- Spec alone (
/review spec:file.md): Extract file list FROM the spec (exclusive source) - Spec + other source (
/review spec:file.md mode:local): Spec provides CONTEXT, other source determines files
File Source Priority (use first available):
$ARGUMENTS.feature-> Search codebase for feature-related files$ARGUMENTS.commit->git show --name-only $ARGUMENTS.commit$ARGUMENTS.mode-> Git diff (pushed or local)$ARGUMENTS.specalone -> Extract files from spec- Default:
mode=local(uncommitted changes)
If mode = "pushed" (or default when no args and clean working tree)
git log origin/$(git rev-parse --abbrev-ref HEAD) -1 --format="%H %s"
git show --name-only --format="" HEAD
git show HEADIf mode = "local" (default)
git diff origin/$(git rev-parse --abbrev-ref HEAD)...HEAD --name-only
git status --porcelain
git diff HEADIf spec provided
- Read the spec file for context (requirements, architecture, expected behavior)
- Spec alone: Extract all referenced files from spec as review targets
- Spec + other source: Use spec as context only, files come from other source
If commit provided
git show --name-only $ARGUMENTS.commit
git show $ARGUMENTS.commitIf feature provided
This is a feature-based review, independent of git changes.
- Use
Task(subagent_type="explore-codebase")to find all files related to the feature - Apply scope filter if provided (backend ->
backend/**/*.go, frontend ->frontend/src/**/*.{ts,tsx}) - Collect the file list from agent response -> these become the review targets
Auto-Categorize Files
| Pattern | Domain |
backend/**/*.go | Backend |
frontend/src/**/*.{ts,tsx} | Frontend |
| Other | Config/Docs |
Apply forced scope if provided: $ARGUMENTS.scope
Report Scope
## Review Scope
**Source**: [feature/mode/spec/commit]
**Feature**: [feature name if provided, otherwise "N/A"]
**Spec Context**: [spec file path if provided, otherwise "None"]
**Commit**: [hash if applicable]
**Detected Scope**: [backend/frontend/both]
### Backend ([count] files)
- [file list]
### Frontend ([count] files)
- [file list]
### Other ([count] files)
- [file list]2. REVIEW (PARALLEL)
MANDATORY: Use Task tool with subagent_type for each agent. Do NOT read files directly.
CRITICAL: Launch ALL applicable agents in a SINGLE message with MULTIPLE tool calls (parallel execution). Do NOT launch one agent, wait for it, then launch the next. Every matching condition below = one agent in the SAME message.
Scale agent count to the actual breadth of the diff and the review dimensions that apply. No upper limit, and do not gate on file counts. Assess the real scope and spawn accordingly:
- Per domain in scope: at least Correctness + Architecture (the floor). Add Performance, Duplication, Test-coverage, and any other applicable dimension as the change warrants.
- One focused agent per (dimension × file-cluster). On a large diff, partition the file set across several agents per dimension so no single agent reviews too many files. More files / more dimensions = more agents, with no cap.
Backend Review (when backend files present, ≥2 agents minimum, no maximum)
- Correctness & Safety -
Task(subagent_type="backend-code-optimizer", prompt="Read and review these Go files for correctness and safety: [file list]. Focus on: error handling, nil safety, context propagation, edge cases, bugs, business logic errors. Spec context: [spec summary if available]. Provide quality score and categorized issues.") - Architecture & Conventions -
Task(subagent_type="backend-code-optimizer", prompt="Read these Go files: [file list]. Then search for similar existing patterns in backend/ to compare against. Focus on: Clean Architecture compliance, layer boundaries, dependency direction, naming conventions, DRY principle. Spec context: [spec summary if available]. Provide quality score and categorized issues.") - Performance (conditional: multi-file or I/O-heavy changes) -
Task(subagent_type="backend-code-optimizer", prompt="Read and review these Go files for performance: [file list]. Focus on: concurrency patterns, query efficiency, N+1 queries, memory allocation, unnecessary copies, context cancellation. Provide categorized issues.") - Duplication scan (conditional: new code added) -
Task(subagent_type="backend-code-optimizer", prompt="Read these new Go files: [new file list]. Then search backend/ for existing code that duplicates the same functionality. Check for reusable helpers, services, and patterns that already exist. Report any duplications found.") - Test coverage -
Task(subagent_type="backend-code-optimizer", prompt="Check test coverage for these Go files: [file list]. For each file, check if a corresponding *_test.go exists. Verify tests cover happy path + error cases. Check if tests follow project patterns (testify, hand-written mocks, *Env struct). Report missing tests and inadequate coverage.")
Frontend Review (when frontend files present, ≥2 agents minimum, no maximum)
- Component Quality & Hooks -
Task(subagent_type="frontend-code-reviewer", prompt="Read and review these React/TypeScript files for correctness: [file list]. Focus on: React patterns, hook dependency arrays, state management, unnecessary re-renders, Shadcn UI usage, error handling. Spec context: [spec summary if available]. Provide quality score and categorized issues.") - TypeScript & Patterns -
Task(subagent_type="frontend-code-reviewer", prompt="Read these React/TypeScript files: [file list]. Then search for similar existing components/hooks in frontend/src/ to compare against. Focus on: type safety, conventions, naming, DRY principle, consistent patterns. Spec context: [spec summary if available]. Provide quality score and categorized issues.") - UX & i18n (conditional: UI component changes) -
Task(subagent_type="frontend-code-reviewer", prompt="Read and review these UI files: [file list]. Focus on: responsive design, loading/error states, accessibility, useTranslations (from next-intl) usage for all user-facing text, proper Shadcn component usage. Provide categorized issues.") - Duplication scan (conditional: new code added) -
Task(subagent_type="frontend-code-reviewer", prompt="Read these new files: [new file list]. Then search frontend/src/ for existing components, hooks, or utilities that duplicate the same functionality. Report any duplications found.")
Supporting (as needed, launched in the SAME message)
| Condition | Task tool call |
| Database changes | Task(subagent_type="explore-db", prompt="dev - Check tables related to [feature]. Verify schema, constraints, RLS") |
| External library | Task(subagent_type="explore-docs", prompt="[library] [specific API] best practices") |
Skip Conditions
- If
scope=frontend-> skip all backend agents entirely - If
scope=backend-> skip all frontend agents entirely - If no frontend files changed -> skip frontend agents
- If no backend files changed -> skip backend agents
- If no files changed at all -> report "No files to review" and stop
Agent outputs to integrate:
- Quality scores -> merge into section 4
- Issues categorized as Critical/Important/Nice-to-have -> merge into section 5
- Optimization recommendations
3. AGGREGATE RESULTS
Aggregate and format the results from section 2 agents. Do NOT re-analyze files yourself.
Use the analysis format from checklists/backend-checklist.md and checklists/frontend-checklist.md.
## Code Review Analysis
### Files Reviewed (from agent reports)
- `path/to/file` - [purpose of changes]4. QUALITY SCORES
Aggregate scores from specialized agents (section 2). Skip domains with no agent output.
Use scoring criteria from checklists.
Global Score
Weighted average based on file count per domain.
## Global Quality Score: X/100
Formula: (Backend Score x backend_files + Frontend Score x frontend_files) / total_files
[1-2 sentence overall assessment]5. PROPOSE FIXES
## Recommended Fixes
### Critical (must fix)
1. **[Issue]**
- File: `path:line`
- Problem: [description]
- Fix: [how to fix]
### Important (should fix)
1. ...
### Nice-to-have
1. ...6. VALIDATE
Ask with AskUserQuestion: "Code review complete. What would you like to do?"
Options:
- "Apply all fixes"
- "Apply Critical only"
- "Apply Critical + Important"
- "No fixes needed"
7. IMPLEMENT (if requested)
This is the core purpose of the review command: identify issues AND fix them.
After user validation, implement fixes directly using Edit tool. Do NOT just report - actually modify the files.
Order:
- Critical issues first
- Important issues
- Nice-to-have (if approved)
Implementation approach:
- Use Edit tool to apply each fix
- Include simplification recommendations from agents
- Apply one fix at a time, verify it doesn't break anything
- Track progress with TodoWrite
Rules:
- Do not break existing functionality
- Do not change business logic unless it's a bug
- Keep changes minimal but complete
- Apply ALL approved fixes, don't stop halfway
- If logic seems wrong, ASK before changing
8. VERIFY
Run verification based on scope:
# Backend (if backend files changed)
cd backend && go build ./... && go vet ./... && golangci-lint run ./... && go test ./...
# Frontend (if frontend files changed)
cd frontend && npm run test:run && npm run buildBackend and frontend tests are MANDATORY: All existing tests must pass (zero regressions).
Database (if schema changes): run get_advisors via explore-db (dev/prod).
9. SUMMARY
Use the summary format from templates/review-report.md.
Rules
- USE AGENTS - Task tool with subagent_type, never analyze directly
- REVIEW IN PARALLEL - launch multiple specialized review agents per scope in a single message
- MEASURE - provide quality scores per domain
- PRIORITIZE - Critical > Important > Nice-to-have
- SIMPLIFY - include simplification recommendations from agents
- FIX WHAT YOU FIND - after user approval, actually implement fixes with Edit tool
- MINIMAL CHANGES - fix issues, don't refactor unless asked
- CHECK i18n - verify
useTranslations(fromnext-intl) for all frontend text - VERIFY BUILDS - run build commands before completing
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.

