km:code-review

Review uncommitted code diffs for design issues, bugs, and rule drift.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers focused on local changes can miss design regressions, dangerous bugs, and deviations from project rules in uncommitted diffs; this Skill surfaces those issues before they reach commits or PRs.

Core Features & Use Cases

  • Reviews uncommitted diffs and prioritizes findings by severity (CRITICAL, HIGH, MEDIUM, LOW) to support commit-blocking decisions.
  • Performs multilayer analysis (function, module, system) and filters lint-only or unchanged-line noise while honoring repository-specific rules.
  • Use cases include pre-commit checks, focused reviews for feature/fix/refactor changes, and preparing a standardized report for reviewers or CI gates.

Quick Start

Review the current uncommitted git changes and generate a prioritized code review report formatted according to report-format.md.

Frequently Asked Questions about km:code-review

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

FAQPage Schema
How do I review uncommitted code changes for design issues and bugs?

Catch design regressions and dangerous bugs in uncommitted diffs by applying multilayer analysis across function, module, and system levels. This surfaces deviations from project rules before changes reach commits or pull requests.

What is the best way to check uncommitted git changes before a commit?

Perform a pre-commit review on uncommitted git diffs that filters lint-only and unchanged-line noise. This generates a standardized, severity-prioritized report to support commit-blocking decisions before changes reach commits.

Can I prioritize code review findings by severity for CI gates?

Yes, you can label code review findings with CRITICAL, HIGH, MEDIUM, and LOW severity levels. This prioritization supports CI gates and commit-blocking decisions by highlighting the most impactful design issues and bugs.

Does code review for uncommitted diffs handle project-specific rules?

Yes, code review for uncommitted diffs honors repository-specific project rules during analysis. It detects project-rule drift in feature, fix, and refactor changes while filtering out lint-only noise.

What limitations exist when reviewing uncommitted code changes?

A key limitation is avoiding lint-only or unchanged-line noise during review. The process focuses strictly on design issues, bugs, and project-rule drift in uncommitted diffs rather than general formatting or style enforcement.