requesting-code-review

Automate structured code review of git-based changes before merging.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/benjgrad/workout-ai --skill requesting-code-review-benjgrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/benjgrad/workout-ai/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/benjgrad/workout-ai --skill requesting-code-review-benjgrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This capability enables teams to catch issues early by routing code changes to a dedicated review workflow, ensuring quality before integration.

Core Features & Use Cases

  • Automated routing of code changes to a code-review subagent for structured feedback.
  • Inline templates and placeholders to capture what was implemented, plan alignment, and feedback.
  • Use Case: In a task-driven feature branch, call for a reviewer after Task 2 to validate changes before merging to main.

Quick Start

Request a code review after completing each task to ensure issues are caught early before merging.

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 structured code reviews before merging a pull request?

Automated code review routes git changes to a subagent for structured feedback, capturing base and head SHAs to enforce a review plan and output a structured report before merging.

What is the best way to catch code issues early in a subagent-driven development cycle?

Subagent-driven code review validates feature work and major refactors by enforcing a structured review plan, capturing implementation details via templates, and generating feedback before integration.

When should I request a code review during feature branch development?

Request a code review after completing each task in a feature branch to validate changes and catch issues early before merging to the main branch.

Does this code review workflow require specific git branch metadata?

The code review workflow captures implementation details using base and head SHAs alongside inline feedback templates to align changes with the original review plan.

Can I use this structured code review for major refactors across git-based projects?

Structured code review applies to major refactors across git-based projects, routing changes to a dedicated subagent to enforce quality assurance before integration.