requesting-code-review

Generate a code reviewer prompt with requirements and git SHAs, then triage findings.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/miptah21/skills --skill requesting-code-review-miptah21
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/miptah21/skills/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/miptah21/skills --skill requesting-code-review-miptah21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you get reliable, requirement-based feedback on code changes before they merge, reducing defects, regressions, and wasted rework.

Core Features & Use Cases

  • Dispatch a code reviewer subagent with focused context: Sends the reviewer only what they need (description, requirements, and git range) to evaluate the change without needing your full session history.
  • Enforce review timing: Uses a clear checklist for mandatory review after each task, after major features, and before merging to main.
  • Turn feedback into action: Prioritizes critical issues for immediate fixes and ensures important issues are resolved before further progress.

Quick Start

Request code review for your latest changes by providing a description, the plan or requirements, and the base/head SHAs to the reviewer template.

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 to verify changes against requirements before merging?

To request a code review, provide a description, the plan or requirements, and the base/head git SHAs to generate a reviewer prompt that verifies changes match quality expectations before integration.

When should I run a pre-merge code review during feature development?

Run pre-merge code review after completing each subagent-driven task, finishing major features, reaching refactoring checkpoints, and validating integration to detect defects early before they cascade.

How does code review triage prioritize feedback for remediation?

Code review triage categorizes feedback into Critical, Important, and Minor remediation actions, prioritizing critical issues for immediate fixes and ensuring important issues are resolved before further progress.

What information does a subagent need to perform a code review?

A subagent code review requires a prompt containing DESCRIPTION, PLAN_OR_REQUIREMENTS, BASE_SHA, and HEAD_SHA to evaluate changes with focused context without needing the full session history.

Can I use code review for subagent-driven development without sharing full session history?

Yes, subagent-driven code review dispatches focused context by sending only the description, requirements, and git range, allowing the reviewer to evaluate changes without needing your full session history.

Does code review work with git ranges to validate merge readiness?

Yes, code review uses base and head git SHAs to define a range, validating merge readiness by verifying that code changes match requirements and code quality expectations before integration.