requesting-code-review

Review git change ranges and triage issues by severity.

4|1|Updated Jan 22, 2026

Search Tags:#quality assurance #code review #pull request #subagent #triage #git diff #release readiness

Ready to run

npx skills add https://github.com/jordanhindo/Turtlez --skill requesting-code-review-jordanhindo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/jordanhindo/Turtlez/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/jordanhindo/Turtlez --skill requesting-code-review-jordanhindo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams reduce defects and regressions by ensuring code changes are reviewed against requirements before they merge into the main branch.

Core Features & Use Cases

Structured review requests: Dispatches a code-reviewer subagent with a consistent template and clear context.
SHAs-based diff review: Reviews changes strictly within a base-to-head git range so feedback maps to the actual delta.
Actionable triage: Applies review feedback by prioritizing Critical and Important issues while tracking Minor items for later.

Quick Start

After completing your next task or major feature, request review by dispatching the code-reviewer subagent and providing {WHAT_WAS_IMPLEMENTED}, {PLAN_OR_REQUIREMENTS}, {BASE_SHA}, {HEAD_SHA}, and {DESCRIPTION}.

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 for a specific git diff range?▼

A SHA-based code review analyzes changes strictly within a base-to-head git range, ensuring that all feedback maps directly to the actual delta committed rather than unrelated pre-existing code.

What's the best way to triage code review feedback before merging to main?▼

Triage code review feedback by prioritizing Critical and Important issues for immediate mitigation, while tracking Minor items for later resolution, ensuring release readiness and preventing requirement drift from reaching main.

When should I use an automated code review subagent during development?▼

Use a code review subagent at subagent-driven development checkpoints, after major feature completion, for pre-merge validation, or during ad-hoc recovery when stuck after complex bug fixes to catch defects early.

What information do I need to provide to initiate a structured pull request review?▼

You need to provide what was implemented, the plan or requirements, the BASE_SHA, the HEAD_SHA, and a description of the change to dispatch the code-reviewer subagent using its consistent template.

Can I use this code review process for ad-hoc recovery after a complex bug fix?▼

Yes, this code review process applies to ad-hoc recovery when stuck or after complex bug fixes, dispatching a subagent to validate the git diff and prevent regressions from reaching the main branch.