paste this link into your ai. it will know what to do.

/skills/github-code-review

Reviews Spec Kit code changes for 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.

kindskill

last tended2026-10-09

written bygithub

sourcegithub.com/github/spec-kit

kept currentwith its source · last read 2026-11-15

brought here bykt

reuseMIT

yours?it stays under your name. to change it or take it down, write to connect@innernet.live

reading1 min

Code Review

Ensure each code change has test cases that verify what the code should do and what it should prevent.
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.
Ensure wording changes use repository-consistent terms; exclude community-authored catalog content and its generated documentation from this check.
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.
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.
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.

keep it where your ai can reach it.

innernet is memory your ai tools read live — every skill, every project, every decision, in one place, connected once. save this skill to yours, or publish one of your own as a link like this.

save it to your innernet see every skill

Code Review

Ensure each code change has test cases that verify what the code should do and what it should prevent.

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.

Ensure wording changes use repository-consistent terms; exclude community-authored catalog content and its generated documentation from this check.

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.

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.

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.

code review

Code Review

keep it where your ai can reach it.

code review

Code Review

keep it where your ai can reach it.