Agent skill

Review

A skill your agent uses to run an independent, clean-context code review of an implemented feature against its spec and acceptance criteria before shipping.

MITAuto-check passedDevelopment

Install Review

skills CLI

$ npx skills add genkovich/sdd --skill review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install genkovich/sdd review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/genkovich/sdd.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/review .claude/skills/review && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "review" agent skill from https://github.com/genkovich/sdd/tree/main/skills/review into .claude/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", 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

$skill-installer install https://github.com/genkovich/sdd/tree/main/skills/review

Type 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.

skills CLI

$ npx skills add genkovich/sdd --skill review -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install genkovich/sdd review --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/genkovich/sdd.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/review .agents/skills/review && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "review" agent skill from https://github.com/genkovich/sdd/tree/main/skills/review into .agents/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", 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.

skills CLI

$ npx skills add genkovich/sdd --skill review -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install genkovich/sdd review --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/genkovich/sdd.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/review .cursor/skills/review && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "review" agent skill from https://github.com/genkovich/sdd/tree/main/skills/review into .cursor/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", 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

$ gemini skills install https://github.com/genkovich/sdd.git --path skills/review

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add genkovich/sdd --skill review -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install genkovich/sdd review --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/genkovich/sdd.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/review .gemini/skills/review && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "review" agent skill from https://github.com/genkovich/sdd/tree/main/skills/review into .gemini/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", 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.

GitHub CLI

$ gh skill install genkovich/sdd review

Installs 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).

skills CLI

$ npx skills add genkovich/sdd --skill review -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/genkovich/sdd.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/review .github/skills/review && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "review" agent skill from https://github.com/genkovich/sdd/tree/main/skills/review into .github/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", 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.

skills CLI

$ npx skills add genkovich/sdd --skill review -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install genkovich/sdd review --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/genkovich/sdd.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/review .opencode/skills/review && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "review" agent skill from https://github.com/genkovich/sdd/tree/main/skills/review into .opencode/skills/review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review", 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
GitHub stars: 171
Token cost: ~1.9k tokens
SKILL.md length: 922 words
Files: 2 (incl. references)
Skills in repo: 21
Repo updated: Sep 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses to run an independent, clean-context code review of an implemented feature against its spec and acceptance criteria before shipping.

Works in 6 steps: Scope the diff. Determine the change… → Dispatch the independent reviewer. Run… → Collect cited findings. Each finding… → …
Run an independent
SKILL.md covers Owner, Inputs, Protocol and Definition of Done, plus 2 more sections
Calls git

What it does

Review is an agent skill from genkovich/sdd. Use to run an independent, clean-context code review of an implemented feature against its spec and acceptance criteria before shipping. Triggers on "review {slug}", "code review the changes for {slug}", "review the diff for {slug}", "is {slug} ready to ship", "/sdd:review {slug}", "переглянь зміни {slug}", "код-рев'ю фічі {slug}", "рев'ю diff". Dispatches the reviewer subagent over the whole feature diff (stage 1 spec/AC compliance, stage 2 quality), collects cited findings, and resolves each with you…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/review-dimensions.md`).

It sits in Development, covering Code review, User stories and Subagents. The repository describes itself as: Spec-Driven Development for Claude Code: 12 atomic Socratic skills + a TDD implement engine (agent-team & dynamic-workflow modes). The licence is MIT.

When your agent uses it

Run an independent
Clean-context code review of an implemented feature against its spec and acceptance criteria before shipping
Code review the changes for {slug}
Review the diff for {slug}

Example prompts

“review {slug}”
“code review the changes for {slug}”
“review the diff for {slug}”
“/review”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Scope the diff. Determine the change under review: git diff ..HEAD on the feature branch (base = the branch point), or the named changed…
Dispatch the independent reviewer. Run the reviewer agent — subagent_type: "sdd:reviewer" (read-only, clean context — it re-reads…
Collect cited findings. Each finding cites file:line + the AC/contract it touches. Drop uncited findings (per the critic discipline). A…
Resolve each finding with the user via AskUserQuestion: Fix now (hand the actionable finding back to implement/the author as a follow-up…
Write the review record. docs/features//_review/review-.md: scope (diff stat), findings with verdicts, and the gate result (PASS / CHANGES…
Verdict + next. Then emit the stage-handoff block per ../_shared/handoff.md — What I did + Review (_review/review-.md) + Run next: PASS →…

What it can do on your machine

Read from SKILL.md and the folder at commit 4403913. 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
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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 loads about 1.9k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 142 tokens; SKILL.md has 922 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~142
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.2k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from genkovich/sdd at commit 4403913, republished under its MIT licence (© genkovich). 922 words, ~1,900 tokens.

Download SKILL.mdSave it as .claude/skills/review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: review
description: Use to run an independent, clean-context code review of an implemented feature against its spec and acceptance criteria before shipping. Triggers on "review {slug}", "code review the changes for {slug}", "review the diff for {slug}", "is {slug} ready to ship", "/sdd:review {slug}", "переглянь зміни {slug}", "код-рев'ю фічі {slug}", "рев'ю diff". Dispatches the reviewer subagent over the whole feature diff (stage 1 spec/AC compliance, stage 2 quality), collects cited findings, and resolves each with you. Hard-refuses if the feature isn't implemented yet.
model: inherit
effort: high
agents: reviewer

Skill: review

The independent review gate. After implement has written + tested + committed the code, review looks at the whole change at once, with fresh eyes — does it actually satisfy every acceptance criterion, and is it good code? This is distinct from the per-task gate inside implement (which proves each task green): review is the cross-cutting, clean-context pass a human reviewer would do on the PR.

It reuses the shared clean-context discipline (../_shared/critic.md) and the reviewer subagent (read-only). Question phrasing per ../_shared/ask-style.md.

Review-record prose follows artifact_language (carry the language in the reviewer's dispatch prompt) — the verdict literals PASS / CHANGES REQUESTED / REVIEW_CLEAN and cited identifiers stay English → ../_shared/artifact-language.md.

Owner

Tech Lead / a reviewer who did not write the code (independence is the point).

Inputs

<slug> — feature slug.
Gate (hard refuse): an implemented change must exist (commits on the feature branch, or a non-empty working diff). Nothing to review → «run implement <slug> first».
Read for the review baseline — the whole AC chain, so the trace can be checked end-to-end: docs/features/<slug>/spec.md §5 (the full AC set — the source of truth, not the diff's trailers), sad.md §6 (the sequence flows/branches each AC should appear in), data-model.md / contracts/openapi.yaml / Accepted adr/ (the contracts the code must honour), test-plan.md (the AC→test map, if a separate file), and tasks.json (which AC each task claimed).

Protocol

Scope the diff. Determine the change under review: git diff <base>..HEAD on the feature branch (base = the branch point), or the named changed files. Note the SDD-AC trailers — the ACs the implementation claims to satisfy.
Dispatch the independent reviewer. Run the reviewer agent — subagent_type: "sdd:reviewer" (read-only, clean context — it re-reads spec/contracts itself, no paraphrase; model per judgment_model; effort xhigh on L/XL via CLAUDE_CODE_EFFORT_LEVEL, per ../_shared/agent-roster.md) — over the diff along the dimensions in ./references/review-dimensions.md: stage 1 — every claimed AC genuinely satisfied and the whole §4 user-story set + §5 AC set traced end-to-end (spec → sequences §6 → data-model → api → tasks → implement): every §4 user story has ≥1 AC and a §6 flow, and every §5 AC reaches code+test — spanning every surface declared in sad.md target_surfaces (a UI AC traces to a component / e2e-through-UI test, not only a backend one) — flagging any user story or AC that dropped out anywhere in the chain, not only the ACs the diff claims via its SDD-AC trailers; stage 2 — conventions, error/edge handling, security, boundary violations, test adequacy. For a large diff, fan out one reviewer per dimension and merge.
Collect cited findings. Each finding cites file:line + the AC/contract it touches. Drop uncited findings (per the critic discipline). A clean review returns REVIEW_CLEAN. If the reviewer ran asynchronously and came back as an idle/completion signal with no report, pull the full report through the host's messaging channel — never accept a verdict without its text (→ ../_shared/agent-roster.md, shared-contract point 2).
Resolve each finding with the user via AskUserQuestion: Fix now (hand the actionable finding back to implement/the author as a follow-up task — re-enter the TDD loop for it) / Defer (record in spec §8 Open questions with owner + due) / Not an issue (the reviewer misread; record why). Never ship an unresolved stage-1 (AC) finding.
Write the review record. docs/features/<slug>/_review/review-<date>.md: scope (diff stat), findings with verdicts, and the gate result (PASS / CHANGES REQUESTED).
Verdict + next. Then emit the stage-handoff block per ../_shared/handoff.md — What I did + Review (_review/review-<date>.md) + Run next: PASS → (/clear, then /sdd:ship <slug>); CHANGES REQUESTED → /sdd:implement <slug> for the fixes (no /clear — stay in context to iterate), then re-review the changed surface.

Show full SKILL.md (349 more words)Show less

Definition of Done

The independent reviewer ran over the whole feature diff (not just per-task).
Every claimed AC was checked for genuine satisfaction; the whole §4 user-story set + §5 AC set was traced end-to-end (spec → sequences → data-model → api → tasks → implement) — every §4 US has ≥1 AC and a §6 flow, every §5 AC reaches code+test — and anything that dropped out anywhere in the chain was flagged, not just the ACs the diff claims. Every in-scope user story / AC is covered or explicitly deferred with owner + due.
Every finding is resolved (fixed / deferred / dismissed-with-reason); no open stage-1 finding remains.
A review record exists with a PASS / CHANGES REQUESTED verdict.
The clean-context reviewer pass (the whole skill is a verifier) is this skill's structural self-check (../_shared/self-check.md); the verdict is its report.

Anti-patterns

Reviewing your own code in the same context that wrote it. The reviewer must be clean-context and, ideally, not the author — that's what catches the blind spots.
Uncited findings. «This feels off» is not actionable — cite file:line + the AC/contract or drop it.
Shipping with an open AC finding. A stage-1 gap means the feature doesn't do what the spec says — fix or explicitly de-scope (spec change), never wave through.
Under-checking added-by-fix ACs. An AC that entered §5 through a bug is proof the spec already missed that case once — trace it at least as strictly as the rest; the fix's pinning test is its floor, not proof of full coverage.
Trusting the diff's SDD-AC trailers as the complete AC set. The trailers only list what the diff claims. Review traces the whole §5 set end-to-end — an AC that never reached the diff (no task wrote it, no test asserts it) is the most dangerous gap precisely because the trailers can't reveal it.
Re-litigating style the repo already settled. Judge against the conventions + contracts, not personal taste.
Treating the per-task gate as the review. Green tests prove each task; they don't prove the change coheres or that the AC are truly met end-to-end.

References & template

./references/review-dimensions.md — the review dimensions + the reviewer dispatch shape.
../_shared/critic.md — the clean-context dispatch discipline this reuses.

Files

SKILL.md and 1 other file (references) in skills/review of genkovich/sdd.

SKILL.md
references/review-dimensions.md

Open the folder on GitHubat commit 4403913

Compare with similar skills

Review 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.

Review compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Review this skillgenkovich/sdd	171	—	~1.9k	Automated safety check: Pass	MIT	1 mo ago
Ad ReviewCorridorTech/PoseCap	224	—	~2.4k	Automated safety check: Notes	Apache-2.0	3 days ago
Implement FeatureLog2n-io/Typhon	250	—	~2k	Automated safety check: Pass	Custom licence	yesterday
Code ReviewOpenHands/extensions	163	—	~2.1k	Automated safety check: Pass	MIT	yesterday
Solo ReviewLeoYeAI/openclaw-master-skills	2.2k	—	~5.6k	Automated safety check: Notes	MIT	2 mo ago
GitHub Review Iterationprisma/orm	48k	—	~2.2k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Ad Review
CorridorTech/PoseCap
Two-axis fresh-context code review per WORKFLOW §10. An agent skill from CorridorTech/PoseCap.
224 GitHub stars~2.4k tokensUpdated 3 days ago
DevelopmentAuto-check: notes
Implement Feature
Log2n-io/Typhon
Implement a GitHub issue end-to-end — scope it (whole issue or specific phases), build an acceptance-criteria plan from its design doc, get the plan approved, then develop autonomously with tests…
250 GitHub stars~2k tokensUpdated yesterday
DevelopmentAuto-check passed
Code Review
OpenHands/extensions
Review code changes for material correctness, security, compatibility, and maintainability risks, grounded in the current repository and acceptance criteria.
163 GitHub stars~2.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Solo Review
LeoYeAI/openclaw-master-skills
Final code review and quality gate — run tests, check coverage, audit security, verify acceptance criteria from spec, and generate ship-ready report.
2.2k GitHub stars~5.6k tokensUpdated 2 mo ago
DevelopmentAuto-check: notes
GitHub Review Iteration
prisma/orm
Official
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
48k GitHub stars~2.2k tokensUpdated yesterday
DevelopmentAuto-check passed
Cherry Studio PR Review
CherryHQ/cherry-studio
Reviews Cherry Studio branches, pull requests, commits, files and docs against the project's own architecture, naming, API-boundary and UI rules, report-only by default.
53k GitHub stars~3.9k tokensUpdated today
DevelopmentAuto-check passed

Questions about Review

What does Review do?

A skill your agent uses to run an independent, clean-context code review of an implemented feature against its spec and acceptance criteria before shipping. Review is an agent skill from genkovich/sdd. Use to run an independent, clean-context code review of an implemented feature against its spec and acceptance criteria before shipping.

When should I use Review?

Review fits situations like: run an independent; clean-context code review of an implemented feature against its spec and acceptance criteria before shipping; code review the changes for {slug}; review the diff for {slug}.

How do I install Review in Claude Code?

Run `npx skills add genkovich/sdd --skill review -a claude-code`. Or copy the skill folder (skills/review in genkovich/sdd) into .claude/skills/review in your project. Claude Code loads it when a task matches its description.

How do I install Review in Codex?

Run `npx skills add genkovich/sdd --skill review -a codex`. Or copy the skill folder (skills/review in genkovich/sdd) into .agents/skills/review in your project. Codex loads it when a task matches its description.

Can I use Review 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 genkovich/sdd --skill review -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, .gemini/skills/review, .github/skills/review and .opencode/skills/review in your project.

What does Review need to run?

Going by SKILL.md and its folder, Review needs the command-line tools its instructions call (git).

Does Review access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Review 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. Review the folder before installing.

What licence does Review use?

Review 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 use?

About 1.9k tokens (SKILL.md is roughly 7.6k 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 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Review?

Skills that share tags, products or a category with Review: Ad Review (CorridorTech/PoseCap, 224 stars), Implement Feature (Log2n-io/Typhon, 250 stars), Code Review (OpenHands/extensions, 163 stars) and Solo Review (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review?

genkovich (a GitHub user) maintains it in genkovich/sdd, which has 171 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on September 5, 2026.

Source: genkovich/sdd on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Review

Install Review

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Skill: review

Owner

Inputs

Protocol

Definition of Done

Anti-patterns

References & template

Files

Compare with similar skills

Similar skills

Ad Review

Implement Feature

Code Review

Solo Review

GitHub Review Iteration

Cherry Studio PR Review

More from genkovich/sdd

Fix

Implement

Interview

Classify Size

Decide Adr

Tasks

Questions about Review

Install Review

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Skill: review

Owner

Inputs

Protocol

Definition of Done

Anti-patterns

References & template

Files

Compare with similar skills

Similar skills

More from genkovich/sdd

Related

Questions about Review