code-review

Layered code review of staged git changes, run against the project's own review checklist. This skill provides the flow and the summary template; it does not assume any specific checklist content.

When to use

• About to commit and want a structured review against the project's existing checklist.
• User asks "run the review checklist over this change".
• Need a layered audit (global prohibitions + per-layer checks) of staged work.

When NOT to use

• Style or formatting feedback — use linters / formatters instead.
• The project has no review checklist yet — see Prerequisites below; this skill will guide the user to create one rather than fabricate content.

Prerequisites

The project root or docs/ contains a review checklist document (any name — common examples: code-review.md, CODE_REVIEW.md, review-checklist.md, .github/CHECKLIST.md). The document should include:

• Global prohibitions — one-strike-veto items that every change must pass.
• Per-layer checks — grouped by code layer / module / concern, one section per layer.

If the project does not yet have this checklist, tell the user: this skill depends on it; suggest sedimenting one (after reviewing this change once, lock in the recurring issues as a checklist). This skill does not generate checklist content for the project.

Steps

1. Locate the checklist Search project root, docs/, .github/ and other common locations for a review checklist document. If multiple exist, ask the user to pick one. If none exists, stop and prompt the user to create one (see Prerequisites).
2. Get the change scope Run git diff and git diff --staged to see all uncommitted code changes (additions, deletions, modifications). Also run git status to see new untracked files. If there are no changes, tell the user "no code changes to review" and stop.

3. Walk through each item Based on the layers/sections the change touches, walk through the corresponding parts of the checklist:

   • All changes: first run through global prohibitions (veto items).
   • Changes touching a specific layer/module: locate the corresponding section in the checklist and check each item.

   For each checklist item, judge whether the changed code passes. Skip layers the change does not touch.

4. Output the review result

   Use this format:

   ## Code Review Result
   
   **Changed files:** <list all changed files>
   **Checklist source:** <document path>
   
   ### Global prohibitions
   - [✅/❌] 1. <check item description>
   ...
   
   ### <layer / module name>
   - [✅/❌] 1. <check item description>: <note>
   ...
   
   ### Issues
   <if any item failed, list specific file, line number, problem description, fix suggestion>
   <if all pass, show "No issues found">

Relationship to other skills

• change-recap — sediments new review items into the checklist (expands checklist content). This skill consumes the checklist to do the review.
• workspace-consistency — the "changes traceable" dimension can invoke this skill to retroactively review a change that lacks review.