requesting-code-review

Dispatch a code reviewer subagent to evaluate changes against requirements.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Sungmaster/Sung --skill requesting-code-review-sungmaster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Sungmaster/Sung/tree/main/.claude/plugins/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/Sungmaster/Sung --skill requesting-code-review-sungmaster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents bugs and architectural issues from cascading by automating the process of requesting a structured, objective code review from a specialized subagent before merging or proceeding to the next task.

Core Features & Use Cases

  • Context-Aware Reviewing: Provides the reviewer with specific git SHAs and requirements, ensuring the evaluation is focused on the work product rather than session history.
  • Standardized Feedback: Categorizes issues into Critical, Important, and Minor, helping developers prioritize fixes effectively.
  • Use Case: After implementing a new feature, use this skill to dispatch a reviewer to verify that the code meets the project's architectural standards and requirements before merging into the main branch.

Quick Start

Use the requesting code review skill to initiate a review of the current changes against the specified plan by providing the base commit, head commit, and task description.

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 before merging a feature branch?

Automate code review by dispatching a subagent to evaluate git changes against defined requirements and quality standards before merging. This provides objective, context-specific technical feedback to prevent the accumulation of technical debt.

What is the best way to provide context for an automated code review?

Provide context for automated code review by supplying specific git SHAs and task descriptions. This ensures the evaluation focuses strictly on the work product rather than session history, verifying that code meets architectural standards.

How does automated code review categorize technical feedback?

Automated code review categorizes technical feedback into Critical, Important, and Minor issue classifications. This standardized feedback helps developers prioritize fixes effectively before proceeding to the next development task.

When do I need to request a subagent code review in my development workflow?

Request a subagent code review after task completion, feature implementation, or before merging branches. This workflow step prevents bugs and architectural issues from cascading by verifying code changes against project requirements.

Can I use git commit SHAs to scope an automated code review?

Yes, you can scope an automated code review using git commit SHAs. The reviewer evaluates code changes by comparing the base commit and head commit against the specified task plan to ensure focused verification.