skills.rest
yt8766
yt8766COMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Dispatch a code-review subagent to assess git changes before merging.

1|Updated Mar 22, 2026
Search Tags:#automation#git#workflow#quality-assurance#code-review#peer-review
One-click install
npx skills add https://github.com/yt8766/learning-agent-core --skill requesting-code-review-yt8766
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/yt8766/learning-agent-core/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/yt8766/learning-agent-core --skill requesting-code-review-yt8766

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce early quality by routing targeted code-review feedback to the right stakeholders, reducing review overhead and preventing issues from slipping into main branches.

Core Features & Use Cases

  • Targeted Review Dispatch: automatically triggers a dedicated code-reviewer subagent for code changes, preserving the author's context.
  • Process Alignment: ensures reviews happen after each task, after major features, or before merging to main.
  • Feedback Synthesis: collects strengths and issues and guides action to fix critical and important items.

Quick Start

Prompt the code-reviewer subagent to evaluate the latest changes and generate a focused review summary.

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 changes to main?▼

Automate code review before merging by dispatching a specialized subagent to assess changes using git SHAs and a plan reference, generating structured feedback with strengths and issues to prevent problems in main branches.

When should I trigger peer review in a task-driven development workflow?▼

Trigger peer review in task-driven development after completing individual tasks, finishing major features, or before merging to main, ensuring targeted evaluation context and early quality enforcement.

What inputs are required to initiate an automated code review workflow?▼

Initiating an automated code review workflow requires git SHAs for change tracking and a plan reference to establish context, enabling the subagent to generate structured feedback output.

Does automated code review work without integrating external dependencies?▼

Yes, automated code review works without external dependencies, operating independently to dispatch a subagent that synthesizes strengths and issues for rapid fixes.

What is the best way to structure feedback for rapid code fixes?▼

The best way to structure feedback for rapid code fixes is to synthesize output into categorized strengths and issues, guiding developers directly to critical and important items needing attention.

How does a code-review subagent preserve author context during workflow automation?▼

A code-review subagent preserves author context by using targeted dispatch for code changes, evaluating modifications against the plan reference and git SHAs without losing the developer's original task framework.

Related Skills

Explore More Software Engineering Skills→
TheBBzTheBBz

subagent-driven-development

Dispatch a subagent per task with code reviews between tasks.

Community
Advanced
ahgraberahgraber
5

code-review

Review diffs and pull requests with structured, actionable feedback.

Community
Advanced
ssiumhassiumha
9

tdd-practices

Guide developers through the RED-GREEN-REFACTOR TDD cycle.

Community
Advanced
conejoRojoconejoRojo

requesting-code-review

Dispatch a subagent to evaluate git-based changes against project requirements.

Community
Advanced