requesting-code-review

Dispatch a code-reviewer subagent with context and structured feedback templates.

1|1|Updated Dec 1, 2025

Search Tags:#git #workflow #quality #review #subagent #code-review

Ready to run

npx skills add https://github.com/shmily1012/AutoWriter --skill requesting-code-review-shmily1012

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/shmily1012/AutoWriter/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/shmily1012/AutoWriter --skill requesting-code-review-shmily1012

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool provides a structured mechanism to trigger and guide code reviews by dispatching a code-reviewer subagent. It ensures reviewers receive focused context about the work product, not the reviewer’s session history, helping prevent scope creep and miscommunication.

Core Features & Use Cases

Contextual Dispatch: Sends precisely crafted context (what was implemented, plan, base/head SHAs) to a reviewer subagent to accelerate and focus feedback.
Session Preservation: Keeps your own session context separate from the review analyst to protect cognitive load and enable smoother iteration.
Workflow Guidance: Enforces review after each task, after major features, and before merges to main to maintain quality.
Use Case: Before merging a feature branch, trigger a code review to ensure adherence to the plan and identify critical issues early.

Quick Start

Trigger a code review immediately after finishing a task by dispatching the code-reviewer subagent with the summary and relevant git SHAs.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema

How do I trigger a code review for a feature branch before merging?▼

To trigger a code review before merging, dispatch the code-reviewer subagent by providing explicit BASE_SHA, HEAD_SHA, a summary of what was implemented, and the planned requirements to receive structured production readiness feedback.

What is a subagent code review and how does it preserve my session context?▼

A subagent code review dispatches a dedicated reviewer to evaluate work products using precisely crafted context. It preserves your session context by keeping the reviewer's analysis separate, preventing scope creep and reducing cognitive load.

What information do I need to provide for an automated code review?▼

You need to provide explicit WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION to generate actionable feedback for production readiness from the code-reviewer subagent.

When should I run a code review workflow during development?▼

You should run a code review workflow after completing each task, after finishing major features, and before merging branches to main to catch issues early and maintain deliverable quality.

Can I use this code review workflow without providing git SHAs?▼

No, providing the BASE_SHA and HEAD_SHA is explicitly required to dispatch the code-reviewer subagent, as these SHAs define the exact scope of the work product for focused feedback.