MCP.Market

code-review skill

by github·github/spec-kit·150k stars·MIT

Reviews Spec Kit code changes for consistency with applicable design documents, positive and negative test coverage, regression evidence for bug fixes, and consistent repository terminology. Use when reviewing a diff or pull request. Do not use for implementing changes or posting GitHub review actions.

A100/100content scan

Is the code-review skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-10-25.

No findings.

Install the code-review skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/github/spec-kit.git /tmp/spec-kit
mkdir -p ~/.claude/skills
cp -r /tmp/spec-kit/.github/skills/code-review ~/.claude/skills/code-review
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Code Review

  1. Ensure each code change has test cases that verify what the code should do and what it should prevent.
  2. Ensure bug-fix pull requests include a regression test that demonstrates the bug was reproducible before the change and is fixed afterward; if the reviewer cannot run the comparison, use available evidence and state that limitation.
  3. Ensure wording changes use repository-consistent terms; exclude community-authored catalog content and its generated documentation from this check.
  4. Identify the affected domains and read the applicable documents in design/ before evaluating architectural consistency. For CLI command changes, use design/cli.md; for agent integrations, use design/integration.md; for workflow step types, use design/workflow-step.md. Read other design documents when relevant, not every document for every PR.
  5. Check the changes against the applicable design requirements, including implementation boundaries, ownership, lifecycle, and delivery requirements. Reference the documents rather than duplicating their rules in this skill. Cite the document and section for each reported mismatch.
  6. Distinguish an unexplained design violation from an intentional design change. Evaluate the rationale and evidence for an intentional change; updating the design document alone does not establish that the implementation is justified.

More skills from github/spec-kit

  • Aadd-community-extensionAdd a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension work.

All agent skills → · MCP servers