requesting-code-review

Dispatch code-reviewer subagents to validate changes against requirements using git SHA ranges.

115|54|Updated May 25, 2026
One-click install
npx skills add https://github.com/totvs/engpro-advpl-tlpp-skills --skill requesting-code-review-totvs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/totvs/engpro-advpl-tlpp-skills/tree/main/skills/superpowers/requesting-code-review
Command: npx skills add https://github.com/totvs/engpro-advpl-tlpp-skills --skill requesting-code-review-totvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents defects and misaligned implementations from propagating by ensuring changes are reviewed against requirements before teams merge or proceed to the next step.

Core Features & Use Cases

  • Review-trigger guidance: Defines mandatory and optional moments to request review across subagent-driven development, plan execution, and ad-hoc changes.
  • Deterministic review dispatch: Standardizes how to compute git base/head SHAs and how to submit a structured request to a code-reviewer subagent using a reusable template.
  • Feedback-driven iteration: Instructs how to act on Critical/Important/Minor findings and how to push back when feedback is incorrect, using technical justification.

Example use case: after completing a large feature, compute the BASE_SHA and HEAD_SHA for that change, dispatch the code-reviewer subagent with a clear summary and plan link, then fix any Critical and Important issues before merging.

Quick Start

Ask the AI to request a code review for the current implementation by providing BASE_SHA and HEAD_SHA and filling the code-reviewer template with your change summary and plan requirements.

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 review for subagent-driven development before merging?

Automate code review by computing the git base and head SHAs for your implementation, then dispatching a code-reviewer subagent with a structured summary to validate changes against requirements before merging.

When should I request a code review during batch plan execution?

Request a code review after completing a large feature or batch plan execution to catch misaligned implementations early, preventing cascading defects from propagating before you proceed to the next step.

How to handle severity triage feedback from a code review?

Handle severity triage by acting on Critical and Important findings immediately, deferring Minor issues, or pushing back with technical justification when the code review feedback is incorrect.

What do I need to provide to run a production readiness check on my git changes?

Provide the BASE_SHA and HEAD_SHA defining your git diff range, along with a change summary and plan requirements, to run a production readiness check via a code-reviewer subagent template.

Does this code review approach work for ad-hoc feature work?

Yes, this code review approach applies to ad-hoc feature work by submitting your git SHA range and change summary to a code-reviewer subagent to ensure early quality checks reduce defects.

How does a code-reviewer subagent validate merge readiness?

A code-reviewer subagent validates merge readiness by analyzing the git SHA range diff against your plan requirements and returning structured severity-based issues to fix, defer, or clarify.