skills.rest
BryceRoberts13
BryceRoberts13COMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Route completed work to a code-review subagent for validation against requirements.

Updated Mar 10, 2026
Search Tags:#automation#git#workflow#subagent#quality-assurance#code-review#review-template
One-click install
npx skills add https://github.com/BryceRoberts13/superpowers-for-antigravity --skill requesting-code-review-bryceroberts13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/BryceRoberts13/superpowers-for-antigravity/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/BryceRoberts13/superpowers-for-antigravity --skill requesting-code-review-bryceroberts13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently validate code changes by routing completed work to a dedicated code-review subagent to ensure requirements are met before merging.

Core Features & Use Cases

  • Automated review routing: Dispatches the code-review subagent immediately after task completion or delivery of major features.
  • Structured feedback framework: Uses a standardized issue template and severity categories to surface critical issues early.
  • Git-aware context: Leverages BASE_SHA and HEAD_SHA to generate precise diffs for reviewers.
  • Use Case: After finishing Task 2 or a major feature, trigger a review to surface gaps before proceeding.

Quick Start

Trigger a code-review pass by dispatching the code-reviewer subagent with the current and base 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 automate code reviews before merging to main?▼

Automate code reviews by routing completed work to a code-review subagent that validates implementation against requirements and produces a prioritized assessment for remediation before merging.

What is the best way to trigger a structured code review after finishing a feature?▼

The best way to trigger a structured code review is by dispatching a code-reviewer subagent with the current and base SHAs to generate a precise diff and enforce a standardized issue template.

How does a subagent use Git SHAs to validate implementation against requirements?▼

The subagent uses the BASE_SHA and HEAD_SHA references to generate a precise diff of your code changes, validating the implementation against the original requirements within a standardized review template.

When do I need to dispatch a code-review subagent in my workflow?▼

Dispatch a code-review subagent after each task completion, after delivering major features, or before merging to main to surface critical issues early using severity categories.

Can I use a standardized review template to surface critical code issues early?▼

Yes, this approach uses a standardized issue template with severity categories to capture Git context and surface critical code issues early for fast and thorough remediation.

Do I need specific dependencies to route completed work to a code-review subagent?▼

No specific dependencies are required to route completed work to a code-review subagent; you simply provide the BASE_SHA and HEAD_SHA to trigger the automated review process.

Related Skills

Explore More Software Engineering Skills→
aberrantCodeaberrantCode
1

requesting-code-review

Reviews a range of commits for defects and requirement compliance.

Community
Intermediate
WesleyMFrederickWesleyMFrederick

requesting-code-review

Dispatch a code-reviewer subagent to review Git changes between BASE_SHA and HEAD_SHA.

Community
Basic
earchibaldearchibald
70

subagent-driven-development

Dispatch fresh subagents per task with two-stage spec and code quality reviews.

Community
Advanced
cloudfieldczcloudfieldcz
7

requesting-code-review

Dispatch the cf-powers:code-reviewer subagent to review code changes and return structured feedback.

Official
Intermediate