skills.rest
N0K0
N0K0COMMUNITY
Explore all skills by this author →
WebsiteGitHub

request-review

Generates severity-categorized code review reports from Git commit SHAs and requirement context.

Updated Mar 28, 2026
Search Tags:#git#quality assurance#code review#development workflow#subagent#merge validation
One-click install
npx skills add https://github.com/N0K0/claude-plugins-backalley --skill request-review-n0k0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: request-review
Source: https://github.com/N0K0/claude-plugins-backalley/tree/main/plugins/process/skills/request-review
Command: npx skills add https://github.com/N0K0/claude-plugins-backalley --skill request-review-n0k0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of undetected code defects, requirement mismatches, and architectural flaws that cascade into larger problems later in development or after deployment, by enforcing timely, focused code reviews at critical workflow checkpoints.

Core Features & Use Cases

  • Focused Review Context: Dispatches a dedicated code-reviewer subagent with precise git SHAs, implementation details, and requirement context, so reviews evaluate the work product rather than the developer's thought process.
  • Mandatory Checkpoint Enforcement: Integrates with subagent-driven development, GitHub Issues-based workflows, and ad-hoc development to require reviews after each task, after major features, and before merging to main.
  • Actionable Feedback Guidance: Provides clear rules for acting on review feedback, including prioritizing critical and important issues, and pushing back on incorrect feedback with technical reasoning.
  • Use Case: A developer building a new feature across 3 subagent tasks can use this skill after each task to catch issues early, avoiding compounded rework, and run a final review before merging to ensure no requirement gaps remain.

Quick Start

Invoke the request-review skill to get a targeted code review of your latest code changes right after you finish implementing a feature or task.

Frequently Asked Questions about request-review

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

FAQPage Schema
How do I catch code defects and requirement mismatches before merging to main?▼

To catch code defects and requirement mismatches before merging to main, you can request a targeted code review by providing the base and head git commit SHAs. This dispatches a dedicated code-reviewer subagent with precise implementation context to generate a severity-categorized review report.

How does subagent-driven code review work for feature development?▼

Subagent-driven code review works by dispatching a dedicated code-reviewer subagent with specific git SHAs and requirement context. This ensures the review evaluates the actual work product rather than the developer's thought process, providing actionable feedback on code defects and architectural flaws.

When do I need to run a code review in a GitHub Issues-based development workflow?▼

You need to run a code review in a GitHub Issues-based workflow at critical checkpoints: after completing each subagent task, after finishing major features, and before merging to main. This enforces mandatory validation to prevent defects from cascading into larger production issues.

What is the best way to validate code changes across multiple subagent tasks?▼

The best way to validate code changes across multiple subagent tasks is to run a focused code review after each task completion. This catches issues early and avoids compounded rework, followed by a final comprehensive review before merging to ensure no requirement gaps remain.

How should I handle incorrect feedback from an automated code review?▼

To handle incorrect feedback from an automated code review, you should push back on the incorrect feedback with clear technical reasoning. The review guidance prioritizes addressing critical and important issues first, while allowing developers to technically justify their implementation choices.

Do I need git commit SHAs to perform a merge validation code review?▼

Yes, you need both the base and head git commit SHAs for the change set to perform a merge validation code review. These SHAs provide the precise implementation context required by the code-reviewer subagent to evaluate the specific code changes accurately.

Related Skills

Explore More Software Engineering Skills→
WesleyMFrederickWesleyMFrederick

requesting-code-review

Dispatch a code-reviewer subagent to review Git changes between BASE_SHA and HEAD_SHA.

Community
Basic
victor-brechbillvictor-brechbill
1

prepare-pr

Rebase a GitHub pull request onto main, apply review fixes, and push.

Official
Advanced
kwam1nakwam1na

requesting-code-review

Dispatch a code-reviewer subagent to enforce merge gates with machine-readable YAML blocks.

Community
Advanced
Next-ofkinNext-ofkin
1

code-review-ai-ai-review

Automate code review with static analysis and AI models.

Community
Advanced