requesting-code-review

Dispatch a code-reviewer subagent with Git SHAs for production-readiness assessment.

Updated Oct 22, 2025
One-click install
npx skills add https://github.com/franroa/chezmoi --skill requesting-code-review-franroa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/franroa/chezmoi/tree/main/dot_opencode/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/franroa/chezmoi --skill requesting-code-review-franroa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that code is reviewed early and often, catching issues before they cascade into larger problems. It standardizes the process of requesting code reviews, making it efficient and effective for both the requester and the reviewer.

Core Features & Use Cases

  • Standardized Request: Guides you to gather Git SHAs and dispatch a code-reviewer subagent using a predefined template.
  • Mandatory Review Points: Specifies when reviews are mandatory (e.g., after each task in subagent-driven development, before merging).
  • Actionable Feedback: Focuses on acting on feedback, fixing critical and important issues immediately.
  • Use Case: After completing a task or a major feature, use this Skill to request a code review. For example, after implementing a new verification function, this Skill will help you dispatch a code-reviewer subagent to check your work against the plan.

Quick Start

Announce skill usage

I'm using the requesting-code-review skill to get feedback on my latest changes.

Example: Dispatching a code-reviewer subagent

(Assuming BASE_SHA and HEAD_SHA are set)

Task tool (superpowers:code-reviewer): Use template at requesting-code-review/code-reviewer.md WHAT_WAS_IMPLEMENTED: "Verification and repair functions" PLAN_OR_REQUIREMENTS: "Task 2 from plan.md" BASE_SHA: "a7981ec" HEAD_SHA: "3df7661" DESCRIPTION: "Added verifyIndex() and repairIndex() with 4 issue types"

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I request a code review before merging changes to main?

Code review requests capture your Git SHAs (BASE_SHA and HEAD_SHA) and dispatch a code-reviewer subagent using a standardized template. This ensures consistent feedback and catches issues before they merge, making it mandatory before main branch integration.

When should I request code review during development?

Request code review after completing each task in subagent-driven development, after major features, and before merging. This includes refactoring and bug fixes. Early, frequent reviews prevent issues from cascading into larger problems.

What's included in a code review request template?

The template captures BASE_SHA and HEAD_SHA, what was implemented, plan or requirements reference, and a description of changes. This standardized workflow ensures reviewers have context and requesters receive actionable feedback on critical and important issues.

Can I use code review in my existing Git workflow?

Yes. Code review integrates into any Git-based development workflow by requiring only Git SHAs and a code-reviewer subagent. It works alongside existing quality assurance and development practices without replacing your current tools.

What happens after I dispatch a code-reviewer subagent?

The code-reviewer subagent produces a production-readiness assessment based on the changes between BASE_SHA and HEAD_SHA. You then act on feedback by fixing critical and important issues immediately before proceeding.

Does code review work for bug fixes and refactoring?

Yes. Code review applies to bug fixes, refactoring, and feature work equally. The templated workflow enforces review at mandatory checkpoints, ensuring all code changes receive feedback before integration.