requesting-code-review

Dispatches a code-reviewer subagent with git diff context to assess production readiness.

Updated May 19, 2026
One-click install
npx skills add https://github.com/davidsunglee/pi-flow --skill requesting-code-review-davidsunglee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/davidsunglee/pi-flow/tree/main/packages/pi-flow-core/skills/requesting-code-review
Command: npx skills add https://github.com/davidsunglee/pi-flow --skill requesting-code-review-davidsunglee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After completing a major feature or before merging to main, code needs an unbiased review, but the session that wrote the code carries generation bias. This Skill dispatches a fresh code-reviewer subagent with precisely crafted git diff context and requirements so issues are caught before they compound. ## Core Features & Use Cases - Structured review dispatch: Builds a review prompt from a template with placeholders for what was implemented, requirements, base/head SHAs, and optional re-review or artifact-output blocks. - Severity-based verdicts: The reviewer returns a parseable verdict (Approved, Approved with concerns, or Not approved) with findings grouped into Critical, Important, and Minor categories, each with file:line references and remediation guidance. - Model and CLI resolution: Resolves the capable model tier and subagent dispatch configuration from flow.json via a shared helper before dispatching with subagent_run_serial. - Use Case: After finishing a standalone feature branch, run this Skill to have a fresh-context reviewer compare the full diff against the plan, then act on the verdict before merging to main. ## Quick Start Ask the agent to request a code review of the current branch against main using the requesting-code-review skill before merging.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I request a code review before merging to main?▼

Determine the git range with git merge-base HEAD main and git rev-parse HEAD, fill the review-code-prompt.md template with what was implemented and the requirements, then dispatch a code-reviewer subagent via subagent_run_serial using the capable model tier.

How does the code reviewer report its verdict?▼

The reviewer outputs a Verdict line in an Outcome block with one of three labels: Approved, Approved with concerns, or Not approved. Findings are grouped under Critical, Important, and Minor headings with file:line references, and Critical findings always force Not approved.

When should I request a code review with this skill?▼

Request review after completing a major feature outside execute-plan, before merging to main, when stuck and needing a fresh perspective, before refactoring as a baseline check, or after fixing a complex bug.

What should I do if the code reviewer is wrong?▼

Push back with technical reasoning rather than implementing suggestions that break things. Reference working tests or code that prove correctness, since the reviewer works only from the diff and provided context.

Does the reviewer see my conversation history?▼

No. The reviewer runs in a fresh context using the capable model tier and receives only the filled prompt template with the git range and requirements, so it evaluates the code without bias from the generation process.