requesting-code-review

Dispatch a subagent to evaluate git diffs against defined requirements.

2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/NagyVikt/codex-plugins --skill requesting-code-review-nagyvikt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/NagyVikt/codex-plugins/tree/main/plugins/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/NagyVikt/codex-plugins --skill requesting-code-review-nagyvikt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of shipping unverified code by providing a structured, subagent-driven review process that catches architectural flaws, bugs, and missing requirements before merging.

Core Features & Use Cases

  • Subagent Dispatch: Automatically triggers a specialized code-reviewer subagent to analyze git diffs.
  • Severity Categorization: Forces a clear distinction between critical bugs, important architectural improvements, and minor stylistic nits.
  • Use Case: Before merging a major feature branch, use this skill to ensure the implementation matches the original plan and meets all production readiness criteria.

Quick Start

Use the requesting-code-review skill to dispatch a code reviewer for the changes between the current branch and main.

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 git diffs before merging to production?

You can standardize code review by dispatching a subagent to analyze git diffs against defined requirements. It categorizes findings by severity, separating critical bugs from architectural improvements and minor stylistic nits.

What is subagent-driven code review and how does it work?

Subagent-driven code review is a process where a specialized subagent is dispatched to systematically assess code quality. It validates git diffs against a structured checklist to ensure production readiness before merging.

How do I categorize the severity of issues found during a code review?

Categorize code review issues by forcing a clear distinction between critical bugs, important architectural improvements, and minor stylistic nits. This severity categorization is applied during the git diff evaluation process.

Does the code review subagent check testing coverage and architecture?

Yes, the dispatched subagent evaluates git diffs to validate code architecture, testing coverage, and implementation accuracy against a structured checklist before approving a branch for merge.

When do I need to use a structured code review workflow?

Use a structured code review workflow before merging a major feature branch to ensure the implementation matches the original plan and catches architectural flaws, bugs, and missing requirements before shipping.