requesting-code-review

Review code changes for production readiness and plan alignment.

1|Updated Feb 20, 2026

Search Tags:#workflow #subagent #quality-assurance #code-review #pull-request #review-process

Ready to run

npx skills add https://github.com/BlackRoad-OS-Inc/blackroad-operator --skill requesting-code-review-blackroad-os-inc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/BlackRoad-OS-Inc/blackroad-operator/tree/main/agents/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/BlackRoad-OS-Inc/blackroad-operator --skill requesting-code-review-blackroad-os-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps teams ensure code quality by routing focused, review-oriented context to a dedicated reviewer, preventing feedback from being diluted by session history.

Core Features & Use Cases

Automated reviewer dispatch: triggers a code-reviewer subagent with precisely crafted context for evaluation.
Structured feedback: uses a standardized review template to surface strengths, issues, and production readiness concerns.
Before merge: verifies that critical issues are addressed and alignment with plan requirements is maintained.
Use Case: after completing a major feature or refactor, request a review to validate implementation and guide subsequent work.

Quick Start

Dispatch a code-review request for the latest changes to validate implementation against the plan.

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 feedback before a pull request merge?▼

Automating code review feedback before a pull request merge involves dispatching a dedicated subagent to evaluate changes against plan requirements. This workflow isolates review context to prevent feedback dilution from session history.

What is the best way to ensure production readiness for new code changes?▼

Ensuring production readiness for new code changes requires surfacing risks through a standardized review template. This validates implementation, identifies critical issues, and confirms alignment with plan requirements before merging.

How does a subagent workflow catch code quality issues early?▼

A subagent workflow catches code quality issues early by routing focused, review-oriented context to a dedicated code-reviewer subagent. This mechanism ensures precise evaluation and provides actionable feedback after each major feature.

When should I request a structured code review during development?▼

You should request a structured code review after completing each task, major feature, or refactor, and before merging. This timing catches implementation issues early and validates alignment with the plan.

Can I validate a major feature refactor against plan requirements automatically?▼

Validating a major feature refactor against plan requirements involves triggering an automated reviewer dispatch. The reviewer subagent evaluates the focused context to verify implementation correctness and surface production readiness concerns.