requesting-code-review

Dispatches a code reviewer subagent to evaluate git diffs against requirements before merging.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/SleyiW/iWana-neXt --skill requesting-code-review-sleyiw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/SleyiW/iWana-neXt/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/SleyiW/iWana-neXt --skill requesting-code-review-sleyiw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent review, letting bugs, architecture flaws, and unmet requirements slip into production. This Skill dispatches a dedicated code reviewer subagent with precisely crafted context so issues are caught early, before they cascade across tasks. ## Core Features & Use Cases - Structured Review Dispatch: Builds a reviewer prompt from a template with placeholders for description, requirements, and git SHAs, keeping the reviewer focused on the work product. - Severity-Categorized Feedback: Returns issues classified as Critical, Important, or Minor with file:line references and a clear merge-readiness verdict. - Workflow Integration: Fits subagent-driven development, plan execution, and ad-hoc development, with mandatory review points after tasks and before merges. - Use Case: After completing a feature task, you capture the base and head commit SHAs, dispatch the reviewer subagent with the plan reference, receive categorized feedback, fix Important issues, and proceed to the next task with confidence. ## Quick Start Ask the AI to request a code review of your latest commits against the task requirements before merging to main.

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?

Capture the base and head commit SHAs with git rev-parse, then dispatch a code reviewer subagent using the provided template with your description, requirements, and SHA range. The reviewer returns categorized issues and a merge-readiness verdict.

How to review code changes with an AI subagent?

Use the Task tool with a general-purpose subagent and fill the code-reviewer template with what was implemented, the plan reference, and the git range. The subagent reviews the diff independently and reports strengths, issues by severity, and recommendations.

When should I request a code review during development?

Request review after each task in subagent-driven development, after completing major features, and before merging to main. It is also valuable when stuck, before refactoring, or after fixing a complex bug.

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

Push back with technical reasoning rather than ignoring the feedback. Show code or tests that prove the implementation works, and request clarification from the reviewer on the disputed point.

What are the limitations of subagent-based code review?

The reviewer only sees the git diff and context you provide, not your session history, so incomplete requirements or missing context can lead to gaps. Critical and Important issues still require manual fixes before proceeding.