requesting-code-review

Reviews code changes and outputs severity-categorized issues with production readiness verdict.

115|13|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Houseofmvps/ultraship --skill requesting-code-review-houseofmvps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Houseofmvps/ultraship/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/Houseofmvps/ultraship --skill requesting-code-review-houseofmvps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unvetted code changes often contain bugs, architecture flaws, or unmet requirements that cause cascading issues and costly rework if merged without review. This Skill eliminates that risk by enforcing a structured, focused code review process before code is merged.

Core Features & Use Cases

  • Dedicated Review Subagent: Dispatches a specialized code-reviewer subagent with precise context (git SHAs, implemented work, original requirements) so the review focuses solely on the code, not the developer's thought process.
  • Severity-Categorized Feedback: Organizes review findings into Critical, Important, and Minor issues with clear fix guidance, so you can prioritize work effectively.
  • Workflow Integration: Supports subagent-driven development (review after each task), plan execution (review after each batch of tasks), and ad-hoc development (review before merge or when stuck).

Quick Start

Use the requesting-code-review skill to run a structured code review on your recent changes by sharing the base and head commit SHAs, a summary of your implemented work, and the original requirements or 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 before merging new git commits?

To automate code review before merging, you provide the base and head git commit SHAs alongside your original requirements. The skill then dispatches a review subagent to analyze the changes and output severity-categorized issues with actionable fix guidance.

What is the best way to structure pre-merge validation for subagent-driven software development?

The best way to structure pre-merge validation for subagent-driven software development is to run a code review after each completed task. This enforces a focused review using git SHAs and original requirements to catch bugs and architecture flaws early.

How does severity categorization work in automated code review?

Severity categorization in automated code review organizes identified issues into Critical, Important, and Minor classifications. This structure helps developers prioritize bug fixes and architecture flaws effectively before delivering a final production readiness verdict.

Can I use this code review process for ad-hoc development when I am stuck?

Yes, you can use this code review process for ad-hoc development when you are stuck or right before a merge. Simply share your implemented work summary and commit SHAs to receive structured feedback and a clear production readiness verdict.

Why do unvetted code changes cause cascading issues in software development?

Unvetted code changes cause cascading issues because they often contain hidden bugs, architecture flaws, or unmet requirements. Implementing a structured pre-merge code review eliminates this risk by enforcing focused validation before integration.