skills.rest
galangryandana
galangryandanaCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Dispatch a code-reviewer subagent to validate changes with structured feedback.

20|1|Updated Dec 10, 2025
Search Tags:#git#workflow#subagent#quality-assurance#code-review#pull-request
One-click install
npx skills add https://github.com/galangryandana/superpowers-for-my-own-workflow --skill requesting-code-review-galangryandana
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/galangryandana/superpowers-for-my-own-workflow/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/galangryandana/superpowers-for-my-own-workflow --skill requesting-code-review-galangryandana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are often delayed or inconsistent. This Skill automates a formal review step by dispatching a code-reviewer subagent to ensure issues are caught early and feedback is standardized.

Core Features & Use Cases

  • Structured review workflow: Enforces a consistent checklist and template-driven feedback.
  • Pre-merge quality gate: Validates changes before merging to main, reducing regression risk.
  • Template-driven feedback and traceability: Uses the WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION placeholders to capture context for reviewers.

Quick Start

Dispatch the code-reviewer subagent with the relevant base SHA, HEAD SHA, and a brief description of the changes to be reviewed.

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 a structured code review before a pull request merge?▼

Automating a structured code review before a merge is done by dispatching a code-reviewer subagent to validate changes. This enforces a consistent checklist and template-driven feedback to catch issues early.

What is the best way to ensure traceable feedback in a git workflow?▼

Ensuring traceable feedback in a git workflow requires using BASE_SHA, HEAD_SHA, and DESCRIPTION placeholders to capture context. This template-driven approach standardizes validation for pre-merge quality gates.

How do I enforce a pre-merge quality gate for feature implementations?▼

Enforcing a pre-merge quality gate for feature implementations involves dispatching a code-reviewer subagent to validate changes. It applies a structured feedback process to reduce regression risk before merging to main.

Can I use a subagent to validate task-based development changes automatically?▼

Yes, you can use a subagent to validate task-based development changes automatically. The skill dispatches a code-reviewer subagent that applies a formal review step to your feature implementations and codebases.

What context do I need to provide for an automated peer-review subagent?▼

Providing context for an automated peer-review subagent requires the WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION placeholders. These ensure structured and traceable feedback validation.

Related Skills

Explore More Software Engineering Skills→
MeechYourGoalsMeechYourGoals
2

requesting-code-review

Dispatch a code-reviewer subagent to identify issues between Git commit SHAs.

Community
Intermediate
ambroviaambrovia

ship

Verify code review and CI status before merging pull requests.

Official
Advanced
AetherCore-DevAetherCore-Dev
9

requesting-code-review

Dispatch a code-reviewer subagent to analyze Git changes between commit SHAs.

Official
Intermediate
miles990miles990

requesting-code-review

Dispatch a code-reviewer subagent to review changes before merging.

Community
Intermediate