requesting-code-review

Dispatches a code-reviewer subagent to review completed tasks before merging.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/irismaker/ai-agent-skills-hub --skill requesting-code-review-irismaker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/irismaker/ai-agent-skills-hub/tree/main/workflow/quality/requesting-code-review
Command: npx skills add https://github.com/irismaker/ai-agent-skills-hub --skill requesting-code-review-irismaker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges the gap between task execution and production-ready code by ensuring code changes are reviewed before merging, reducing defects and guiding reviewers with clear context.

Core Features & Use Cases

  • Dispatch a code-reviewer subagent with precisely crafted context so reviewers evaluate the work product, not the author's history.
  • Support review after completing tasks in subagent-driven development, after major feature implementations, and before merges to main.
  • Integrate template prompts for WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION to standardize feedback.

Quick Start

Dispatch the code-reviewer subagent after completing a task to trigger a formal code review.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I automate a structured code review before merging a major feature?

To automate a structured code review before merging, dispatch a code-reviewer subagent with context like BASE_SHA, HEAD_SHA, and requirements. This bridges task execution and production-ready code by standardizing feedback and preventing defects.

What context do I need to provide for a subagent-driven code review?

A subagent-driven code review requires context placeholders: WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION. Providing this precisely crafted context ensures reviewers evaluate the work product objectively.

When should I trigger a formal code review in a subagent workflow?

In a subagent workflow, trigger a formal code review after completing tasks that may impact production, after major feature implementations, and before merges to main. This early review prevents defects from propagating downstream.

Does structured code review help with defect prevention before pulling requests?

Structured code review helps with defect prevention before pulling requests by guiding reviewers with clear context. Dispatching a code-reviewer subagent ensures changes are evaluated against requirements rather than author history.

Can I standardize pull request feedback using a code-reviewer subagent?

You can standardize pull request feedback using a code-reviewer subagent. It uses template prompts for implementation details and commit ranges to ensure consistent, structured reviews across different tasks and features.