skills.rest
doitian
doitianCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

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

14|1|Updated Dec 29, 2011
Search Tags:#automation#git#workflow#development#subagent#quality-assurance#code-review
One-click install
npx skills add https://github.com/doitian/dotfiles-public --skill requesting-code-review-doitian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/doitian/dotfiles-public/tree/main/ai/workflows/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/doitian/dotfiles-public --skill requesting-code-review-doitian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables early-stage, structured code review by dispatching a dedicated code-reviewer subagent to catch issues before they cascade.

Core Features & Use Cases

  • Review after each task in subagent-driven development to prevent issue escalation.
  • Verify major feature implementations before merging to main and ensure alignment with plan.
  • Optional: request a fresh perspective when stuck or before refactoring to baseline progress.

Quick Start

Submit your change and dispatch the subagent with what was implemented, the plan or requirements, and the BASE/HEAD SHAs to initiate a review.

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

Automate structured code reviews by dispatching a dedicated reviewer subagent with your implemented changes, requirements, and BASE_SHA and HEAD_SHA references to catch issues before they cascade. This standardizes early-stage review using structured templates.

When should I trigger a code review in a subagent-driven development workflow?▼

Trigger code review after completing each task in subagent-driven development, after finishing major features, and before merging to main. You can also request a review when stuck or before refactoring to baseline progress.

What inputs do I need to provide to initiate a code review subagent?▼

Provide the implemented changes, the plan or requirements, and the BASE_SHA and HEAD_SHA references. You also need to fill out templates for what was implemented and the requirements or plan to standardize the review.

Can I get a fresh perspective on my code when stuck or before refactoring?▼

Yes, you can dispatch a code review subagent to get a fresh perspective when stuck or before refactoring. This helps baseline your progress and catch issues early before they escalate into larger problems.

What's the best way to catch code issues before they cascade in a development workflow?▼

Dispatch a dedicated code-reviewer subagent after each task to perform early-stage structured reviews. Standardize the process using BASE_SHA and HEAD_SHA references along with templates for what was implemented and the requirements.

Does this code review workflow require any specific dependencies or components?▼

No specific dependencies or components are required. The workflow operates by dispatching a reviewer subagent using your git changes, requirements, and SHA references to perform structured early-stage code reviews.

Related Skills

Explore More Software Engineering Skills→
alffeialffei
69

requesting-code-review

Dispatch a code-reviewer subagent to validate git changes before merging.

Community
Intermediate
Clay-HHKClay-HHK
2

requesting-code-review

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

Community
Intermediate
zhanglongxiao111zhanglongxiao111
35

requesting-code-review

Dispatch structured code-review tasks for git-based changes with severity categorization.

Community
Intermediate
AetherCore-DevAetherCore-Dev
9

requesting-code-review

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

Official
Intermediate