requesting-code-review

Dispatches a dedicated reviewer to inspect code changes and categorize severity of defects.

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill requesting-code-review-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/workflow/requesting-code-review
Command: npx skills add https://github.com/ajsai47/holyclaude --skill requesting-code-review-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of missed code defects that cascade into production bugs, wasted developer context from self-review, and inconsistent review processes that delay merges and reduce overall code quality.

Core Features & Use Cases

  • Dedicated Review Subagent: Dispatches an isolated code-reviewer subagent with precise change context, so feedback focuses on the work product rather than your thought process.
  • Structured Review Workflow: Enforces review checkpoints after individual tasks, major feature completions, and pre-merge steps, with clear issue severity categorization (Critical, Important, Minor) for prioritized fixes.
  • Multi-Workflow Integration: Works with subagent-driven development, plan-based execution, and ad-hoc development workflows to fit your existing process.
  • Use Case: After implementing a new payment processing feature, use this Skill to get a structured review of your changes against the original requirements, catch missing error handling for failed transactions, and fix critical issues before merging to main.

Quick Start

Ask the AI to request a code review for your most recent code changes against the original feature requirements before you merge 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 automate code review before merging to main?

Automated code review dispatches a dedicated subagent with isolated change context to catch defects before merging to main. It enforces structured review checkpoints after task completion, categorizing issues by severity so you can prioritize critical fixes pre-merge.

What is a structured code review workflow in software development?

A structured code review workflow enforces quality gates at specific development milestones—after individual tasks, feature completions, and pre-merge steps. It categorizes issues by severity (Critical, Important, Minor) to provide prioritized, consistent feedback without manual review coordination.

Can I use a subagent-driven code review for ad-hoc feature work?

Yes, this code review approach works with subagent-driven development, plan-based execution, and ad-hoc feature workflows. It dispatches a dedicated reviewer subagent with precise change context, ensuring feedback targets the work product across all development styles.

How do I catch missing error handling in new features before production?

Catching missing error handling requires a structured code review against original feature requirements before merging. A dedicated subagent analyzes your change context to identify missing edge cases and categorizes them by severity to prevent production bugs.

Does automated code review preserve developer working context?

Automated code review preserves developer context by dispatching an isolated subagent to evaluate changes. The subagent focuses entirely on the work product rather than your thought process, providing severity-categorized feedback without requiring you to self-review.

When should I run a pre-merge code quality checkpoint?

Pre-merge code quality checkpoints should run after individual tasks, major feature completions, and immediately before merging to main. This ensures severity-categorized review feedback catches critical defects early, preventing cascading production bugs without manual review coordination.