m-requesting-code-review

Automate code review requests and categorize issues by severity.

2|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/mituso89/Spec-Driven-Development-toolkits --skill m-requesting-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: m-requesting-code-review
Source: https://github.com/mituso89/Spec-Driven-Development-toolkits/tree/main/m-requesting-code-review
Command: npx skills add https://github.com/mituso89/Spec-Driven-Development-toolkits --skill m-requesting-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of requesting code reviews, ensuring that code quality is maintained and issues are caught early.

Core Features & Use Cases

  • Automated Code Review: Dispatches a reviewer subagent to analyze code commits and provide feedback.
  • Severity Triage: Categorizes findings by severity (Critical, Important, Minor).
  • Integration with Workflows: Seamlessly integrates with various development workflows.
  • Use Case: Before merging a feature branch, use this Skill to ensure that all critical issues are addressed.

Quick Start

Request a code review for the latest commit by running: m-requesting-code-review review --base SHA-1 --head SHA-2.

Frequently Asked Questions about m-requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review for a specific commit range?

Automate code review by running a command specifying the base and head SHA-1 hashes. The Skill dispatches a reviewer subagent to analyze the commits, categorizing issues by Critical, Important, or Minor severity.

How does subagent technology work for analyzing code commits?

Subagent technology dispatches a dedicated reviewer agent to analyze specified code commits. The subagent inspects the changes, identifies issues, and returns feedback categorized by severity levels for integration into development workflows.

Can I use automated code review before merging a feature branch?

Automated code review fits pre-merge workflows by analyzing feature branch commits. It ensures critical issues are addressed before integration, maintaining code quality and catching problems early in the development cycle.

What's the best way to triage code quality issues found in commits?

Triage code quality issues using automated severity categorization. The review subagent separates findings into Critical, Important, and Minor levels, helping prioritize which problems require immediate attention before merging.

Do I need access to the codebase to run an automated code review?

Codebase access is required for automated code review. The Skill needs to read the repository contents and utilize subagent tools to perform commit analysis and generate accurate severity-based feedback.

Why use subagent-based code review over manual commit inspection?

Subagent-based code review provides automated, consistent analysis across commit ranges, categorizing issues by severity. This approach catches critical problems early and integrates seamlessly into existing development workflows without manual effort.