diff-summary

Classify git diff files by role and risk into structured summaries.

4|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/osouthgate/agent-plus --skill diff-summary-osouthgate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diff-summary
Source: https://github.com/osouthgate/agent-plus/tree/main/diff-summary/skills/diff-summary
Command: npx skills add https://github.com/osouthgate/agent-plus --skill diff-summary-osouthgate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and summarize changes in a git diff by automatically classifying each modified file into roles (source/test/config/doc/generated/build/fixture/migration) and assigning a risk tier, enabling rapid, focused reviews without reading every file content.

Core Features & Use Cases

  • Per-file role classification and risk scoring with aggregated stats.
  • Highlights public-api touches and co-changed-test indicators to guide reviewer focus.
  • Works on working tree, staged changes, or explicit ranges to accelerate PR sanity checks and pre-PR workflows.

Quick Start

Run diff-summary to generate a structured, risk-aware summary for the current diff.

Frequently Asked Questions about diff-summary

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

FAQPage Schema
How do I triage a git diff for code review without reading every changed file?

Triage a git diff by classifying modified files into roles like source, test, or config, and assigning risk tiers to produce a structured summary. This enables focused code reviews without reading every file's content.

What is the best way to assess PR risk levels across repository changes?

Assess PR risk levels by analyzing diff metadata and file paths to output per-file risk tiers and aggregate metrics. It highlights public API touches and co-changed test indicators to guide reviewer focus on critical areas.

Can I summarize staged changes or do I need a committed branch comparison?

You can summarize staged changes directly. The triage works on working tree, staged changes, or explicit commit ranges to accelerate PR sanity checks and pre-PR workflows.

Does diff triage work for pre-PR checks on working tree modifications?

Diff triage works for pre-PR checks on working tree modifications. It processes current uncommitted changes and explicit ranges to generate risk-aware summaries for branch comparisons across repositories.

How does file role classification identify API touches in a patch?

File role classification identifies API touches by analyzing diff metadata and file paths to flag public-api modifications. It outputs a structured summary with per-file roles, risk levels, and co-changed test indicators.

What are the limitations of automated diff summarization for code reviews?

Automated diff summarization relies on diff metadata and file paths rather than deeper semantic analysis of file content. It classifies roles and assigns risk tiers to guide focus, but does not replace reading critical source modifications.