requesting-code-review

Request code reviews for git commit ranges before merge.

131|4|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill requesting-code-review-alphalab-ustc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/superpowers/requesting-code-review
Command: npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill requesting-code-review-alphalab-ustc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify completed code changes before they cause regressions, merge conflicts, or production issues by routing the work to a dedicated code review subagent.

Core Features & Use Cases

  • Early Review for Safety: Request review after completing a task, major feature, or refactor to catch issues while they are still cheap to fix.
  • Structured Review Workflow: Gather git commit SHAs, dispatch the reviewer with a clear implementation summary and requirements, and act on feedback by severity.
  • Practical Use Case: After finishing a feature branch, use this Skill to have the changes checked for correctness, architecture, testing gaps, and readiness to merge.

Quick Start

Ask the AI to request a code review for your latest changes and summarize the findings by severity.

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 completed git commits before merging?

The Skill validates merge readiness by comparing git commit ranges, checking requirement alignment, and routing the code changes to a subagent that returns severity-based feedback.

What is the best way to check feature branches for requirement gaps and regressions?

Checking feature branches for requirement gaps involves routing the completed changes to a dedicated code review subagent. This process detects bugs, validates requirements, and confirms production readiness before merge.

Can I use this code review workflow for refactoring tasks and subagent-driven development?

Yes, you can use this code review workflow for refactoring tasks and subagent-driven development. It applies to feature delivery and pre-merge validation, detecting correctness, architecture, and testing gaps for production readiness.

How does the code review subagent handle feedback and merge readiness issues?

The code review subagent handles feedback by categorizing issues based on severity. It checks correctness, architecture, and testing gaps, allowing you to act on feedback by priority before validating production readiness.

Do I need to provide git commit SHAs to validate code changes for production readiness?

Yes, you need to provide git commit SHAs to validate code changes. The Skill uses the commit range comparison to identify specific changes, align them with requirements, and detect bugs before merge.