code-review
Use when completing tasks, requesting review, or receiving code review feedback — covers both requesting and responding to reviews with technical rigor
What this skill does
# Code Review
## Overview
Covers both sides of code review: requesting reviews (dispatching reviewer subagents) and receiving feedback (verifying before implementing suggestions).
## Requesting Review
After completing implementation, dispatch two reviews in order:
### 1. Spec Compliance Review
Route to Codex CLI (read-only):
```bash
${CLAUDE_PLUGIN_ROOT}/skills/plan-and-execute/codex-runner.sh \
"Review code for spec compliance. Spec: [requirements]. Files: [paths]. Report: APPROVED or NEEDS CHANGES with specifics." \
read-only /path/to/project
```
Fail-closed: if Codex returns exit `20`, ask user for explicit approval before any Claude/Sonnet fallback.
Optional fallback only when `CODEX_FAIL_CLOSED=0`: `Task(prompt, model:"sonnet", subagent_type:"superpower-router:code-reviewer")`
### 2. Code Quality Review
Only after spec compliance passes. Route to Codex CLI (read-only):
```bash
${CLAUDE_PLUGIN_ROOT}/skills/plan-and-execute/codex-runner.sh \
"Review code quality. Files: [paths]. Check: naming, error handling, DRY, YAGNI, test coverage. Report: Strengths, Issues (Critical/Important/Minor), APPROVED or NEEDS CHANGES." \
read-only /path/to/project
```
### Review Loop
If reviewer finds issues → fix → re-review → repeat until approved.
## Receiving Review Feedback
When YOU receive feedback, apply technical rigor:
| Step | Action |
|------|--------|
| 1 | Read feedback carefully — don't skim |
| 2 | Verify each suggestion is technically correct before implementing |
| 3 | If suggestion seems wrong, research it (WebSearch, docs) before disagreeing |
| 4 | If genuinely wrong, explain why with evidence — don't just agree |
| 5 | Implement valid suggestions, explain rejections |
### Red Flags
- **Never** agree performatively — verify first
- **Never** implement suggestions blindly without understanding why
- **Never** skip re-review after fixing issues
- **Never** start quality review before spec compliance passes
## Reviewer Agent Prompt
See `./code-reviewer.md` for the detailed reviewer agent prompt template.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.