mt-review-diff

Review code diffs for architectural and implementation issues with structured reports.

Updated May 15, 2026
One-click install
npx skills add https://github.com/t-miura-024/tools --skill mt-review-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mt-review-diff
Source: https://github.com/t-miura-024/tools/tree/main/chezmoi/dot_config/opencode/skills/mt-review-diff
Command: npx skills add https://github.com/t-miura-024/tools --skill mt-review-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of reviewing code changes consistently by providing a structured process for analyzing branch and working tree diffs from both architectural and implementation perspectives.

Core Features & Use Cases

  • Two-Level Diff Review: Evaluates changes through macro architecture checks and micro code-level checks to identify design issues and implementation details.
  • Structured Review Reports: Separates required fixes from optional improvements using consistent severity, recommendation, and review criteria.
  • Use Case: Review a pull request or local code changes by analyzing intent, validating the implementation against goals, and producing a detailed review report.

Quick Start

Use the mt-review-diff skill to review the current branch changes and generate a structured code review report.

Frequently Asked Questions about mt-review-diff

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

FAQPage Schema
How do I review a git diff for architectural and implementation issues?

To review a git diff, this Skill analyzes code differences through macro architecture checks and micro code-level checks. It evaluates branch and working tree changes to identify design issues and implementation details, then generates a structured review report.

What is the best way to structure pull request reviews for actionable feedback?

Structured pull request reviews separate required fixes from optional improvements using consistent severity and review criteria. This process validates implementation against goals and produces detailed reports for actionable code quality assessment.

Can I use this to review uncommitted local code changes?

Yes, you can review uncommitted local code changes. The Skill applies diff analysis to working tree changes, evaluating both architectural intent and implementation-level details to provide structured feedback workflows.

How does a two-level diff review improve software quality?

A two-level diff review improves software quality by evaluating changes through macro architecture checks and micro code-level checks. This dual analysis identifies both high-level design issues and granular implementation problems.

What background context is needed for a branch review?

A branch review requires background context extraction and specific review criteria. Providing this context allows the analysis to validate the implementation against your goals and produce a formatted reporting output.

Does this Skill work without external dependencies?

Yes, the Skill operates with no external dependencies. It independently analyzes code differences to identify architectural issues and implementation-level problems for structured code quality assessment.