diff-analysis

Name: diff-analysis
Availability: InStock
Author: jacob-balslev

Analyze unified git diffs to extract semantic changes and risk surface.

1|Updated May 6, 2026

Search Tags:#blast radius #git diff #patch analysis #unified diff #changeset review #semantic delta #risk surface

Ready to run

npx skills add https://github.com/jacob-balslev/skill-graph --skill diff-analysis-jacob-balslev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diff-analysis
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/diff-analysis
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill diff-analysis-jacob-balslev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diff analysis prevents agents from misreading changesets by helping them separate real semantic impact from formatting noise and identify the likely blast radius before acting.

Core Features & Use Cases

Unified diff anatomy mastery: Interprets diff --git, ---/+++, and @@ hunks to understand where and how changes land.
Semantic-vs-format separation: Classifies changes (rename/move, mechanical rewrite, local logic edit, contract edit, test-only edit) to focus on meaning.
Blast-radius and risk surface naming: Infers downstream areas that could be impacted and frames what must be verified next.
Intent vs diff comparison: Checks whether stated change goals match the actual patch effects.

Quick Start

Use the diff-analysis skill to analyze the proposed patch in a git diff output for semantic deltas, likely blast radius, and verification needs.

Frequently Asked Questions about diff-analysis

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

FAQPage Schema

How do I analyze a git diff to understand the semantic impact of my changeset?▼

Analyzing a unified git diff involves parsing diff structures like `diff --git` and `@@` hunks to separate real semantic changes from formatting noise, classify file-level edits, and estimate the blast radius before commit or review.

What is blast radius estimation in a patch review workflow?▼

Blast radius estimation in patch analysis infers downstream areas that could be impacted by a changeset, helping to frame specific verification needs and identify the risk surface before a code review or commit.

How can I check if my stated commit intent matches the actual git diff output?▼

Checking intent against a git diff requires interpreting hunks with context to compare stated change goals against actual patch effects, ensuring the changeset logic aligns with the originally stated commit intent.

Does diff analysis work with test-only edits and contract changes in a unified diff?▼

Diff analysis classifies changeset types including test-only edits, contract edits, and mechanical rewrites, interpreting the unified diff structure to focus on semantic meaning rather than formatting churn across code and contracts.

How do I separate real code logic edits from formatting churn in a changeset?▼

Separating logic edits from formatting churn requires classifying changeset types like rename, move, and mechanical rewrite, allowing you to focus on actual semantic deltas rather than superficial patch noise.

When should I enforce stated-boundary exclusions during changeset review?▼

Enforcing stated-boundary exclusions during changeset review is necessary when analyzing patch risk surface, ensuring the diff analysis respects scope limits and ignores irrelevant hunks outside the defined boundaries.