requesting-code-review

Coordinate production-readiness code reviews by dispatching a reviewer subagent with git diff context.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/otto-poblysh/pedagemy-early-access --skill requesting-code-review-otto-poblysh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/otto-poblysh/pedagemy-early-access/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/otto-poblysh/pedagemy-early-access --skill requesting-code-review-otto-poblysh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents quality regressions by ensuring every meaningful change is evaluated before it spreads through the codebase.

Core Features & Use Cases

  • Mandatory review gates: after each subagent task, after major features, and before merging to main.
  • High-signal reviewer context: dispatches a purpose-built code-reviewer subagent with a targeted git range and clear implementation vs requirements mapping.
  • Actionable triage workflow: categorize feedback by severity (Critical/Important/Minor) and drive follow-up fixes or justified pushback.

Quick Start

Request a code review for your latest changes by providing BASE_SHA, HEAD_SHA, what you implemented, and the requirements you were following.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I automate a pre-merge code review using a git diff?

Automate a pre-merge code review by dispatching a subagent with your git diff range and implementation requirements to assess quality, testing, and architecture. The process categorizes issues by severity and returns a clear merge readiness verdict.

What is a subagent workflow for merge readiness validation?

A subagent workflow for merge readiness dispatches a dedicated code-reviewer with targeted git context to compare implementations against requirements. It evaluates code quality and architecture, categorizes issues by severity, and returns a production-readiness verdict.

How do I categorize code review issues by severity before merging?

Categorize code review issues by severity through an actionable triage workflow that separates feedback into Critical, Important, and Minor buckets. This drives follow-up fixes or justified pushback before providing a final merge readiness verdict.

When do I need to run a production-readiness code review?

Run a production-readiness code review at mandatory gates: after each subagent task, after completing major feature batches, and before merging changes to main. This prevents quality regressions from spreading through the codebase.

Can I review major feature batches without losing implementation context?

Review major feature batches by providing a dedicated subagent with high-signal context, including the BASE_SHA, HEAD_SHA, and requirement mappings. This ensures the reviewer compares the implementation directly against the original plan requirements.

Does this code review process work without external dependencies?

The code review process works without external dependencies, using a built-in subagent-driven development workflow to validate changes. It requires only your git diff range and the specific requirements you were following to execute the review.