القائمة
Use after completing an implementation task or major feature, and before claiming ready/merge, to verify the work meets requirements via a focused reviewer subagent.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use after an implementation plan exists and it contains independent tasks that can be delegated to fresh subagents in the current session.
Use after planning/brainstorming when implementation begins for any feature or bugfix, before writing production code; requires tests first and red-green verification.
Use after an approved design/spec or clear requirements exist and before implementing a multi-step task; creates a task-by-task implementation plan before code changes.
Use after making code changes, before committing, or when the user asks to "simplify", "clean up", or "review" recent edits — runs three parallel review agents (reuse, quality, efficiency) over the diff and fixes the findings.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or evaluating a plan/design. Relentlessly explores user intent, requirements, trade-offs, and decision branches before implementation.
| name | requesting-code-review |
| description | Use after completing an implementation task or major feature, and before claiming ready/merge, to verify the work meets requirements via a focused reviewer subagent. |
Dispatch a pi reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.
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. Dispatch code-reviewer subagent:
Dispatch a reviewer subagent with the template at ./code-reviewer.md:
subagent({ agent: "reviewer", task: <filled template>, context: "fresh" })
The subagent tool comes from the pi-subagents extension.
Placeholders:
{WHAT_WAS_IMPLEMENTED} - What you just built{PLAN_OR_REQUIREMENTS} - What it should do{BASE_SHA} - Starting commit{HEAD_SHA} - Ending commit{DESCRIPTION} - Brief summary3. 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)
[Dispatch pi reviewer subagent]
WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
PLAN_OR_REQUIREMENTS: Task 2 from docs/pi/plans/deployment-plan.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
[Subagent 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]
Subagent-Driven Development:
Manual Batch Execution:
Ad-Hoc Development:
Terminal Gate:
Never:
If reviewer wrong:
See template at: ./code-reviewer.md (resolve relative to this SKILL.md).