review-spd
Findings-first code review workflow for AI coding agents. Use when the user asks to review uncommitted changes, commits in a date range, or a branch compared to the main branch / PR-style diff. Focuses on bugs, regressions, correctness risks, missing tests, security/data-safety issues, and other behavior-changing defects.
Profile →npx skills add zhu1090093659/spec_driven_develop --skill review-spd --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Review SPD You are executing the **Review SPD** workflow: a findings-first review of changed code. Identify bugs, regressions, and behavior risks introduced by the changes. Do not turn this into a style review or a broad summary. ## Configuration | Item | Default | Purpose | |:-----|:--------|:--------| | Context script | `scripts/review-context.py` relative to this Review SPD skill directory | Collect stable git context | | Default target | Uncommitted changes | Working tree + staged changes | | Commit range default | Last 3 days | Only when the user requests commit/date review without dates | | PR base | Auto-detect `origin/main`, `origin/master`, then remote default branch | Base for branch-vs-main review | | Output style | Findings first | Findings by severity before summaries | References: reviewer sub-agent template `references/reviewer-template.md`; final output format `references/output-format.md`. ## Target Modes Three mutually exclusive targets: 1. **Uncommitted mode** (default) 2. **Commit-range mode** — no explicit range → last 3 days 3. **Branch / PR mode** — branch vs. main or explicit `base` Conflict priority: `branch` specified → branch mode; else `since`/`until`
- Configuration
- Target Modes
- Phase 1: Target Resolution
- Phase 2: Context Collection
- Phase 3: Review Planning
- Phase 4: Sub-Agent Review
- Phase 5: Finding Consolidation
- Phase 6: Final Response
- Review Discipline
python <review-spd-skill-dir>/scripts/review-context.py python <review-spd-skill-dir>/scripts/review-context.py --since "3 days ago" python <review-spd-skill-dir>/scripts/review-context.py --since 2026-06-28 --until 2026-07-01 python <review-spd-skill-dir>/scripts/review-context.py --branch feature/foo python <review-spd-skill-dir>/scripts/review-context.py --branch feature/foo --base origin/main
What does the review-spd skill do?
Findings-first code review workflow for AI coding agents. Use when the user asks to review uncommitted changes, commits in a date range, or a branch compared to the main branch / PR-style diff. Focuses on bugs, regressions, correctness risks, missing tests, security/data-safety issues, and other behavior-changing defects.
How do I install it?
Run `npx skills add zhu1090093659/spec_driven_develop --skill review-spd --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From zhu1090093659/spec_driven_develop, a repository with 958 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.