code-review

Orchestrate chunk-reviewers to evaluate git diffs for quality and correctness.

25|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/toongri/oh-my-toong-playground --skill code-review-toongri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/toongri/oh-my-toong-playground/tree/main/skills/code-review
Command: npx skills add https://github.com/toongri/oh-my-toong-playground --skill code-review-toongri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Pre-merge diffs are hard to vet because reviewers must juggle git metadata, contextual files, and targeted verification while obeying no-modification rules; this Skill centralizes that orchestration so every change is reviewed for quality, correctness, and production readiness before merge.

Core Features & Use Cases

  • Input-mode aware guidance: Supports PR numbers or URLs, branch comparisons, and auto-detection, each with its own requirements gate for metadata extraction, user confirmation, and reference checking.
  • Chunk-reviewer orchestration: Parses diffs, constructs chunk-wise git commands, and dispatches chunk-reviewers while locking the orchestrator to read targeted code, synthesize critiques, and enforce the “no raw git diff or file edits” guardrails.
  • Verification safety guardrails: Enumerates allowed/forbidden context (git stats, CLAUDE.md, chunk results), enforces single-question dialogs for clarification, and keeps constraints such as direct code reading for findings verification and severity adjudication.

Quick Start

Ask the code-review skill to inspect the current diff so it can orchestrate chunk-reviewers, verify contexts, and synthesize the walkthrough before merge.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for git diffs before merging?

You can automate code review for git diffs by orchestrating chunk-reviewers that parse metadata, read targeted code, and synthesize quality critiques before merging. This enforces read-only verification workflows without modifying files.

What is chunked diff review and how does it work?

Chunked diff review splits large git diffs into manageable pieces, dispatches targeted chunk-reviewers to evaluate each segment, and synthesizes their findings. The orchestrator parses git stats and references while locking the system to read targeted code only.

Can I review pull request diffs using branch comparisons or auto-detection?

Yes, pull request diffs support branch comparisons, PR numbers or URLs, and auto-detection contexts. Each input mode has specific requirements gates for metadata extraction, user confirmation, and context budget verification before dispatching chunk-reviewers.

Does the code review workflow modify files during diff verification?

No, the code review workflow forbids file modification during diff verification. The orchestrator locks chunk-reviewers to read targeted code directly, verify findings, and adjudicate severity while enforcing strict no raw git diff and no file edit guardrails.

What's the best way to evaluate merge readiness for large branch diffs?

Evaluating merge readiness for large branch diffs is best handled by chunk-reviewer orchestration that parses git stats, checks CLAUDE.md context, and dispatches targeted reviews. This ensures quality, correctness, and production readiness before merging without file modifications.

Do I need to provide CLAUDE.md context for pre-merge code review?

Yes, providing CLAUDE.md context is required for pre-merge code review as the orchestrator parses it alongside git metadata and chunk results. This context ensures chunk-reviewers apply correct constraints and verification workflows during diff evaluation.