requesting-code-review

Dispatch a code-reviewer subagent to identify defects and readiness issues in completed code changes.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/greglamb/macos-name-tag-app --skill requesting-code-review-greglamb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/greglamb/macos-name-tag-app/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/greglamb/macos-name-tag-app --skill requesting-code-review-greglamb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent defects from reaching production by requesting focused code reviews before merging changes or moving on from completed tasks.

Core Features & Use Cases

  • Targeted Review Requests: Dispatch a code-reviewer subagent with precise implementation context and requirements.
  • Structured Feedback: Evaluate code quality, architecture, testing, requirements coverage, and production readiness by severity.
  • Use Case: After completing a major feature, use this Skill to compare the implementation against its plan, identify critical and important issues, and address feedback before merging.

Quick Start

Use the requesting-code-review skill to review the changes in the current branch against the main branch before merging.

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 before merging a pull request?

To request a code review, provide git commit SHAs, implementation context, and requirements details to dispatch a code-reviewer subagent for severity-based feedback on production readiness before merging.

What is the best way to identify defects in completed code changes before they reach production?

Identify defects in completed code changes by applying this Skill to major feature completions, complex bug fixes, or refactoring baselines to evaluate code quality, architecture, and requirements coverage by severity before production.

Can I use this code review process for subagent-driven development tasks?

Yes, you can use this code review process for subagent-driven development tasks by supplying the implementation context and requirements to validate the changes and address critical issues before moving on.

What do I need to provide to get structured feedback on my branch?

You need to provide git commit SHAs, implementation context, requirements or plan details, and access to a code-reviewer subagent to receive structured severity-based feedback on your branch.

When should I run a pre-merge validation check on my code?

Run a pre-merge validation check when completing major features, complex bug fixes, or refactoring baselines to compare the implementation against its plan and catch cascading code issues before merging.