// Use when completing tasks, implementing major features, or before merging to verify work meets requirements
| name | requesting-code-review |
| description | Use when completing tasks, implementing major features, or before merging to verify work meets requirements |
Run a focused code review pass before changes cascade. Use the review rubric in code-reviewer.md; if a separate reviewer harness is available, give it only the relevant context, not the whole session history. Otherwise perform the review yourself from a clean diff.
Core principle: Review early, review often.
Mandatory:
Optional but valuable:
1. Get git SHAs:
BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
HEAD_SHA=$(git rev-parse HEAD)
2. Run the review pass:
Use the rubric at code-reviewer.md. Prefer a separate reviewer process if available; otherwise review the diff directly in the current session.
Placeholders:
{DESCRIPTION} - Brief summary of what you built{PLAN_OR_REQUIREMENTS} - What it should do{BASE_SHA} - Starting commit{HEAD_SHA} - Ending commit3. Act on feedback:
[Just completed Task 2: Add verification function]
You: Let me request code review before proceeding.
BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)
[Run code review using code-reviewer.md]
DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
PLAN_OR_REQUIREMENTS: Task 2 from docs/codemini/plans/deployment-plan.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
[Review returns]:
Strengths: Clean architecture, real tests
Issues:
Important: Missing progress indicators
Minor: Magic number (100) for reporting interval
Assessment: Ready to proceed
You: [Fix progress indicators]
[Continue to Task 3]
Executing Plans:
Ad-Hoc Development:
Never:
If reviewer wrong:
See template at: requesting-code-review/code-reviewer.md
Generate a CodeWiki project requirements report in Markdown format from an existing codebase. Same report scope as the HTML CodeWiki—presented as `.md` for plain-text reading, Git diffs, and Markdown previewers.
Generate a CodeWiki project requirements report in interactive HTML format from an existing codebase. Same report scope as the Markdown CodeWiki—browser-openable with search, filters, collapsible API cards, and inline SVG/CSS diagrams.
Use when starting any conversation - establishes how to find and use Codemini skills before acting
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes