requesting-code-review

Name: requesting-code-review
Availability: InStock
Author: enigmaicon-eng

Request structured code reviews with severity-based triage for git commit ranges.

1|Updated May 16, 2026

Search Tags:#git #quality assurance #code review #requirements validation #merge readiness #severity triage #subagent workflow

Ready to run

npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill requesting-code-review-enigmaicon-eng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill requesting-code-review-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you avoid regressions and quality issues by ensuring newly completed work is evaluated against requirements before it reaches the main branch.

Core Features & Use Cases

Early, frequent review prompts: requests review after each subagent task, after major features, and before merging.
Requirement-aligned reviewer context: provides a structured brief to the reviewer subagent so the review focuses on the work product, not session history.
Actionable feedback triage: applies a severity-based model (Critical/Important/Minor) and drives clear next steps (fix now, fix before proceeding, or note for later).
Git-based change scoping: reviews a specific range using BASE_SHA and HEAD_SHA to keep feedback grounded in actual diffs.

Quick Start

After finishing a task or a major feature, request a code review by setting BASE_SHA and HEAD_SHA for the commit range, then dispatch the code reviewer subagent with DESCRIPTION and PLAN_OR_REQUIREMENTS filled in.

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 for a specific git commit range?▼

A pre-merge code review evaluates completed work against requirements using a scoped git commit range to catch regressions before changes reach the main branch. It provides structured reviewer context and severity-based triage for clear merge readiness.

How does severity-based triage work in a pre-merge code review?▼

To request a code review, define the git commit range using BASE_SHA and HEAD_SHA, then provide a DESCRIPTION and PLAN_OR_REQUIREMENTS to scope the review to the actual diffs. This ensures feedback is grounded in the specific changes made.

Can I use subagent workflows for continuous code review during feature development?▼

Severity-based triage categorizes review feedback into Critical, Important, and Minor issues to drive clear next steps. This model dictates whether to fix immediately, fix before proceeding, or note for later to ensure merge readiness.

What context does a code reviewer need to validate merge readiness accurately?▼

Yes, subagent-driven development supports early, frequent review prompts after each subagent task and major feature completion. This approach ensures newly completed work is evaluated against requirements before cascading issues or merging.

When should I request a code review checkpoint in my development process?▼

A code reviewer needs four structured context fields: DESCRIPTION, PLAN_OR_REQUIREMENTS, BASE_SHA, and HEAD_SHA. This brief ensures the review focuses strictly on the work product and actual git diffs rather than session history.