skills.rest
Clay-HHK
Clay-HHKCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Route code changes to a reviewer workflow for pre-merge quality assurance.

2|Updated Apr 12, 2026
Search Tags:#git#workflow#code review#subagent#quality-assurance#pre-merge#reviewer
One-click install
npx skills add https://github.com/Clay-HHK/claude-config --skill requesting-code-review-clay-hhk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Clay-HHK/claude-config/tree/main/skills/superpowers/requesting-code-review
Command: npx skills add https://github.com/Clay-HHK/claude-config --skill requesting-code-review-clay-hhk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures changes are reviewed early to catch issues before they cascade, improving quality and alignment with requirements.

Core Features & Use Cases

  • Standardized review prompts: generate structured feedback requests including what was implemented, the plan, and key decisions.
  • Early feedback loop: supports reviews after each task, after major features, and before refactoring.
  • Audit-ready documentation: keeps a traceable review history to facilitate accountability and deployment readiness.

Quick Start

Submit a code-review request by dispatching the code-reviewer subagent with the implemented change set, the planned requirements, and brief context.

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 pre-merge code reviews for feature branches?▼

To automate pre-merge code review, this Skill routes code changes to a dedicated reviewer subagent by dispatching structured prompts containing the implemented change set, planned requirements, and context. It captures feedback and ensures decision points are documented before deployment.

When should I request a code review during development?▼

You should request a code review after completing a task-based development step, finishing major feature work, or before refactoring. Requesting reviews early catches issues before they cascade and improves alignment with planned requirements.

How do I document code review plans and feedback for audit readiness?▼

To document code review plans and feedback, the Skill generates standardized review prompts and maintains a traceable review history. This audit-ready documentation captures key decisions, planned requirements, and feedback-based outcomes for accountability.

What is the best way to generate structured feedback requests for git workflow changes?▼

The best way to generate structured feedback requests is to dispatch the code-reviewer subagent with the implemented change set and brief context. This creates standardized prompts detailing what was implemented, the plan, and key decisions.

Can I use this code review workflow for task-based development across any software project?▼

Yes, this code review workflow is applicable to task-based development, major feature work, and pre-merge checks across software projects. It requires no specific dependencies and fits general git workflows to improve quality assurance.

Related Skills

Explore More Software Engineering Skills→
DaFumDaFum

requesting-code-review

Orchestrate a code-reviewer subagent to generate structured feedback on implemented changes.

Community
Intermediate
brmatolabrmatola

requesting-code-review

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

Community
Basic
andresharpeandresharpe
53

verify

Run privacy, git cleanliness, and push status verification gates.

Community
Intermediate
RangeyRoverRangeyRover
3

speckit.checker

Run static analysis across multiple languages and generate prioritized issue reports.

Community
Intermediate