km:review

Orchestrate multi-phase code reviews on pull requests or diffs.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/koumatsumoto/agent-config --skill km-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: km:review
Source: https://github.com/koumatsumoto/agent-config/tree/main/templates/skills/review
Command: npx skills add https://github.com/koumatsumoto/agent-config --skill km-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews uncommitted changes end-to-end with selectable depth to ensure intent alignment, design, quality attributes, external diagnostics, and documentation before committing.

Core Features & Use Cases

  • End-to-end orchestration: coordinates multiple review phases (intent, code, quality, expert) based on the requested depth.
  • Depth-based control: selects thorough, standard, or quick review scopes with skip logic and aggregation.
  • Reporting & blocking: aggregates results into a single report and blocks merges when critical issues are found.

Quick Start

Run the review orchestrator on a diff or pull request to conduct the configured sequence of reviews and generate a consolidated report.

Frequently Asked Questions about km:review

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

FAQPage Schema
How does automated code review handle pull requests before merging?

Automated code review orchestrates multi-phase reviews on pull requests, analyzing intent, code, quality, and expert-level checks to ensure alignment and quality before merging. It generates a consolidated report and can block merges when critical issues are found.

What is depth control in a multi-phase code review workflow?

Depth control in code review allows selecting thorough, standard, or quick review scopes. It applies skip logic and aggregation across intent, code, quality, and expert phases, ensuring the workflow matches the required validation level for the diff.

Can I block a pull request merge based on code review findings?

Yes, you can block a pull request merge based on code review findings. The orchestrator enforces skip or block decisions automatically when CRITICAL or HIGH severity issues are detected during the review phases.

What is the best way to review uncommitted changes for intent alignment?

The best way to review uncommitted changes for intent alignment is running an end-to-end review orchestrator on the diff. It coordinates intent, code, and quality checks with configurable depth before committing to ensure full alignment.

Does this code review workflow require external diagnostic tools?

No, this code review workflow operates independently without external dependencies. It orchestrates internal review phases for intent, code quality, and expert checks, applying skip logic and aggregating results into a single report.