requesting-code-review

Automate code review requests and consolidate reviewer feedback.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bearhedge/APE-YOLO --skill requesting-code-review-bearhedge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/bearhedge/APE-YOLO/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/bearhedge/APE-YOLO --skill requesting-code-review-bearhedge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of requesting code reviews and collecting reviewer feedback to ensure changes are thoroughly vetted before merging.

Core Features & Use Cases

  • Automated review prompts: Dispatches a code-reviewer subagent for tasks or major changes to surface issues early.
  • Structured feedback workflow: Guides reviewers with a consistent template including WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION.
  • Workflow flexibility: Supports task-driven development, feature work, and pre-merge validation across teams.
  • Audit trail and accountability: Maintains a clear record of review prompts and responses for compliance and traceability.

Quick Start

Trigger a code review by dispatching the code-reviewer subagent and filling the template at code-reviewer.md. Provide the required placeholders: WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, DESCRIPTION. After feedback is returned, address critical and important issues before proceeding.

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 requesting a code review for a pull request?

You can automate requesting a code review by dispatching a subagent with structured prompts containing placeholders like BASE_SHA, HEAD_SHA, and DESCRIPTION to guide the review process and consolidate feedback.

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

Triggering a code review requires filling a template with specific placeholders: WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION to ensure structured feedback.

Can I use structured code review workflows for pre-merge validation?

Yes, structured code review workflows support pre-merge validation by dispatching a subagent to surface issues early, maintaining an audit trail of review prompts and responses for compliance.

How does a subagent consolidate reviewer feedback for major feature implementations?

A subagent consolidates reviewer feedback by using a consistent template that guides reviewers through the changes, ensuring critical and important issues are addressed before proceeding with feature work.

Does task-driven development require structured prompts for code review?

Yes, task-driven development requires structured prompts for code review to automate the dispatch of a code-reviewer subagent and maintain accountability through a clear record of review responses.

What is the best way to streamline peer reviews with structured feedback?

The best way to streamline peer reviews is automating the request process with a subagent, using a template of implementation details and git SHAs to guide reviewers and surface issues early.