CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.
Install Review Spd
$ npx skills add zhu1090093659/spec_driven_develop --skill review-spd -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zhu1090093659/spec_driven_develop review-spd --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/zhu1090093659/spec_driven_develop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/spec-driven-develop/skills/review-spd .claude/skills/review-spd && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "review-spd" agent skill from https://github.com/zhu1090093659/spec_driven_develop/tree/main/plugins/spec-driven-develop/skills/review-spd into .claude/skills/review-spd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-spd", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zhu1090093659/spec_driven_develop/tree/main/plugins/spec-driven-develop/skills/review-spdType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zhu1090093659/spec_driven_develop --skill review-spd -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zhu1090093659/spec_driven_develop review-spd --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zhu1090093659/spec_driven_develop.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/spec-driven-develop/skills/review-spd .agents/skills/review-spd && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-spd" agent skill from https://github.com/zhu1090093659/spec_driven_develop/tree/main/plugins/spec-driven-develop/skills/review-spd into .agents/skills/review-spd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-spd", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zhu1090093659/spec_driven_develop --skill review-spd -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zhu1090093659/spec_driven_develop review-spd --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zhu1090093659/spec_driven_develop.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/spec-driven-develop/skills/review-spd .cursor/skills/review-spd && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "review-spd" agent skill from https://github.com/zhu1090093659/spec_driven_develop/tree/main/plugins/spec-driven-develop/skills/review-spd into .cursor/skills/review-spd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-spd", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zhu1090093659/spec_driven_develop.git --path plugins/spec-driven-develop/skills/review-spd--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zhu1090093659/spec_driven_develop --skill review-spd -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zhu1090093659/spec_driven_develop review-spd --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zhu1090093659/spec_driven_develop.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/spec-driven-develop/skills/review-spd .gemini/skills/review-spd && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "review-spd" agent skill from https://github.com/zhu1090093659/spec_driven_develop/tree/main/plugins/spec-driven-develop/skills/review-spd into .gemini/skills/review-spd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-spd", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zhu1090093659/spec_driven_develop review-spdInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zhu1090093659/spec_driven_develop --skill review-spd -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zhu1090093659/spec_driven_develop.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/spec-driven-develop/skills/review-spd .github/skills/review-spd && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "review-spd" agent skill from https://github.com/zhu1090093659/spec_driven_develop/tree/main/plugins/spec-driven-develop/skills/review-spd into .github/skills/review-spd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-spd", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zhu1090093659/spec_driven_develop --skill review-spd -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zhu1090093659/spec_driven_develop review-spd --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zhu1090093659/spec_driven_develop.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/spec-driven-develop/skills/review-spd .opencode/skills/review-spd && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "review-spd" agent skill from https://github.com/zhu1090093659/spec_driven_develop/tree/main/plugins/spec-driven-develop/skills/review-spd into .opencode/skills/review-spd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-spd", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
review-spd- GitHub stars
- 987
- Token cost
- ~1.5k tokens
- SKILL.md length
- 673 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.
- Works in 6 steps: Target Resolution → Context Collection → Review Planning → …
- The user asks to review uncommitted changes
- SKILL.md covers Configuration, Target Modes, Phase 1: Target Resolution and Phase 2: Context Collection, plus 5 more sections
- Runs Python scripts from its folder; calls python
What it does
Review Spd is an agent skill from zhu1090093659/spec_driven_develop. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/output-format.md`, `references/reviewer-template.md` and `scripts/review-context.py`).
It sits in Development, covering Spec-driven development and Task breakdown. It works with GitHub and Git. The repository describes itself as: Spec-driven development workflow for AI coding agents: architecture-first planning, task decomposition, GitHub Issue/PR tracking, Deep Discuss, and adaptive control for Claude… The licence is MIT.
When your agent uses it
- The user asks to review uncommitted changes
- Commits in a date range
- A branch compared to the main branch / PR-style diff
Example prompts
- “/review-spd”
Requirements
- Python 3
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 14f8c0f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Review Spd loads about 1.5k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 673 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from zhu1090093659/spec_driven_develop at commit 14f8c0f, republished under its MIT licence (© zhu1090093659). 673 words, ~1,529 tokens.
Download SKILL.mdSave it as
.claude/skills/review-spd/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- review-spd
- description
- 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.
- version
- 1.0.1
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:
- Uncommitted mode (default)
- Commit-range mode — no explicit range → last 3 days
- Branch / PR mode — branch vs. main or explicit
base
Conflict priority: branch specified → branch mode; else since/until → commit-range mode; else uncommitted. base applies only to branch mode. Vague requests ("review this") → uncommitted mode; "recent commits" without dates → --since "3 days ago".
Phase 1: Target Resolution
Resolve the context script from the installed Review SPD skill directory, not from the repository being reviewed:
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/mainWhen reviewing this repository itself, the convenience wrapper scripts/review-context.py is also available.
Phase 2: Context Collection
Run the script with cwd = the repository under review (it cd's to the git root itself). The script only collects git context; it does not judge correctness. From its output identify: review mode and base/head, commit list (if any), changed files and diff stats, added/deleted/renamed files, and the unified diff hunks needing semantic review.
If the script reports no changes, stop and say there is nothing to review. Do not invent findings.
Phase 3: Review Planning
Classify review size:
- Small (≤3 files, localized diff): cover Correctness + Tests.
- Medium (multiple files / behavior-affecting): add Regression/Compatibility.
- Large or high-risk (broad changes, auth/permissions, persistence, migrations, concurrency, caching, money, security, public APIs, generated code, config/deployment): add Security/Data Safety + Performance/Concurrency.
Prioritize behavior code, public contracts, data handling, error paths, configuration, persistence, tests. Deprioritize docs, formatting-only changes, generated files, lockfile churn unless they affect runtime behavior.
Phase 4: Sub-Agent Review
If the platform supports sub-agents, spawn focused reviewers using references/reviewer-template.md; otherwise perform the same focused reviews sequentially yourself. Coverage must not shrink without sub-agents.
Reviewer focuses:
- Correctness / Bug Risk: logic errors, edge cases, state consistency, exception paths, invalid assumptions.
- Regression / Compatibility: changed API contracts, config behavior, data formats, migrations, CLI behavior, backward compatibility.
- Tests / Verification: missing tests for changed behavior, weak assertions, stale tests, untested failure modes.
- Security / Data Safety: authorization, validation, injection, secrets, destructive operations, data loss, privacy.
- Performance / Concurrency: async races, caching errors, resource leaks, excessive work, ordering bugs.
Each reviewer returns only evidence-backed candidate findings for its own focus.
Show full SKILL.md (221 more words)Show less
Phase 5: Finding Consolidation
Merge reviewer outputs into one findings list:
- Every finding must be supported by the diff or directly relevant context, with a file:line reference when possible.
- No style preferences, speculative rewrites, or generic best practices unless they create a concrete bug risk.
- Incomplete evidence → move to
QuestionsorResidual Risks, notFindings. - Deduplicate overlaps; keep the clearest impact statement.
- Order by severity: Critical, High, Medium, Low.
Severity guide:
- Critical: data loss, security bypass, production outage, irreversible corruption, severe user impact likely.
- High: clear bug/regression in a common or important path.
- Medium: edge-path bug, compatibility break, missing validation, or test gap likely to hide regressions.
- Low: minor bug risk, confusing behavior, narrow edge case, maintainability issue with direct defect potential.
Phase 6: Final Response
Use references/output-format.md. Findings are the primary focus: present them first, keep summaries brief, never bury a bug below a summary. No findings → explicitly state No findings and include residual risks or testing gaps.
Review Discipline
- Think like a code reviewer, not a feature planner: does the change introduce new bugs?
- Verify claims against code context before reporting.
- Prefer one strong finding over many weak suggestions.
- Do not modify files unless the user explicitly asks you to fix the findings.
- If tests/builds are needed to validate a suspected issue, name the exact command or missing coverage.
© zhu1090093659, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references) in plugins/spec-driven-develop/skills/review-spd of zhu1090093659/spec_driven_develop.
- SKILL.md
- references/output-format.md
- references/reviewer-template.md
- scripts/review-context.py
Open the folder on GitHubat commit 14f8c0f
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in zhu1090093659/spec_driven_develop, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Review Spd next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Review Spd this skillzhu1090093659/spec_driven_develop | 987 | — | ~1.5k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Speckit Git Remotekunstmusik/blue | 154 | 6 repos | ~393 | Automated safety check: Pass | GPL-3.0 | |
| Speckit Taskstoissuesforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~315 | Automated safety check: Pass | Apache-2.0 | |
| Blueprint Construction Planneraffaan-m/ECC | 277k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT |
Similar skills
Speckit Git Remote
kunstmusik/blue
Detect Git remote URL for GitHub integration. An agent skill from kunstmusik/blue.
Speckit Taskstoissues
foryourhealth111-pixel/Vibe-Skills
Convert tasks from tasks.md into GitHub issues. An agent skill from foryourhealth111-pixel/Vibe-Skills.
Blueprint Construction Planner
affaan-m/ECC
Turns a one-line objective into a multi-step plan file with PR-sized steps, context briefs, a dependency graph, parallel-step detection and an adversarial review.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
More from zhu1090093659/spec_driven_develop
Spec Driven Develop
zhu1090093659/spec_driven_develop
Automates pre-development workflow for large-scale complex tasks.
Deep Discuss
zhu1090093659/spec_driven_develop
结构化深度讨论 Skill，用于与用户进行多轮问题分析和方案设计。当用户描述一个问题现象、故障表现、 技术困惑、方案选择困难，或明确说"讨论一下"、"帮我分析"、"我遇到一个问题"、"你觉得怎么样"、 "帮我想想"、"我在纠结"时，必须使用本 skill。当用户提供了一段描述（可能附带截图）并期望深入分析 而非直接给答案时，也应触发本…
Related
Categories
Questions about Review Spd
What does Review Spd do?
Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop. Review Spd is an agent skill from zhu1090093659/spec_driven_develop. Findings-first code review workflow for AI coding agents.
When should I use Review Spd?
Review Spd fits situations like: the user asks to review uncommitted changes; commits in a date range; A branch compared to the main branch / PR-style diff.
How do I install Review Spd in Claude Code?
Run `npx skills add zhu1090093659/spec_driven_develop --skill review-spd -a claude-code`. Or copy the skill folder (plugins/spec-driven-develop/skills/review-spd in zhu1090093659/spec_driven_develop) into .claude/skills/review-spd in your project. Claude Code loads it when a task matches its description.
How do I install Review Spd in Codex?
Run `npx skills add zhu1090093659/spec_driven_develop --skill review-spd -a codex`. Or copy the skill folder (plugins/spec-driven-develop/skills/review-spd in zhu1090093659/spec_driven_develop) into .agents/skills/review-spd in your project. Codex loads it when a task matches its description.
Can I use Review Spd in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zhu1090093659/spec_driven_develop --skill review-spd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-spd, .gemini/skills/review-spd, .github/skills/review-spd and .opencode/skills/review-spd in your project.
What does Review Spd need to run?
Going by SKILL.md and its folder, Review Spd needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Review Spd access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Review Spd safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Review Spd use?
Review Spd is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Review Spd use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 932 tokens, read only when the agent opens those files.
What are the alternatives to Review Spd?
Skills that share tags, products or a category with Review Spd: CCPM Project Management (automazeio/ccpm, 8.4k stars), Speckit Git Remote (kunstmusik/blue, 154 stars), Speckit Taskstoissues (foryourhealth111-pixel/Vibe-Skills, 3.6k stars) and Blueprint Construction Planner (affaan-m/ECC, 277k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review Spd?
zhu1090093659 (a GitHub user) maintains it in zhu1090093659/spec_driven_develop, which has 987 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on July 26, 2026.
Source: zhu1090093659/spec_driven_develop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.