How do I install the Diff Analysis skill?

Run npx skillmds add tools-only/diff-analysis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Diff Analysis safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Diff Analysis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Diff Analysis free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Diff Analysis?

tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Diff Analysis by tools-only — Agent Skill

Name: Diff Analysis
Rating: 4.2 (5 reviews)
Author: tools-only

Diff Analysis

Methodology for categorizing changes, assessing risks, and creating summaries from any changeset. Triggers: diff analysis, changeset review, risk assessment, change categorization, semantic analysis, release preparation, change summary, git diff Use when: analyzing specific changesets, assessing risk of changes, preparing release notes, categorizing changes by type and impact DO NOT use when: quick context catchup - use catchup instead. DO NOT use when: full PR review - use review-core with pensive skills. Use this skill for systematic change analysis with risk scoring.

tools-only 0092355 3 files · 7.7 KB Updated Sep 8, 2026 7 repo stars

File contents

Diff Analysis Methodology

Overview

Structured method for analyzing changesets: categorize changes, assess risks, generate insights. Works for git diffs, configuration changes, API migrations, schema updates, or document revisions.

When to Use

Extracting insights from raw change data
Categorizing and prioritizing changes before code reviews
Preparing release notes or changelogs
Assessing migration scope and risk

Activation Patterns

Trigger Keywords: diff, changes, release notes, changelog, migration, impact, risk assessment

Auto-Load When: Git diffs present, change analysis requested, impact assessment needed.

Progressive Loading

Load modules based on workflow stage:

Always Load

modules/semantic-categorization.md for change categorization workflow

Conditional Loading

modules/risk-assessment-framework.md when risk assessment is needed
modules/git-diff-patterns.md when working with git repositories

Integration

Use sanctum:git-workspace-review for git data gathering
Use imbue:evidence-logging for capturing analysis evidence
Use imbue:structured-output for formatting final deliverables

Required TodoWrite Items

diff-analysis:baseline-established
diff-analysis:changes-categorized
diff-analysis:risks-assessed
diff-analysis:summary-prepared

Mark each item complete as you finish the corresponding step.

4-Step Methodology

Step 1: Establish Baseline (`diff-analysis:baseline-established`)

Define comparison scope: what states are being compared, boundary of analysis, and scale metrics.

For git contexts, load modules/git-diff-patterns.md. For other contexts, compare relevant artifacts.

Step 2: Categorize Changes (`diff-analysis:changes-categorized`)

Group changes by semantic type. Load modules/semantic-categorization.md for change categories, semantic categories, and prioritization.

Step 3: Assess Risks (`diff-analysis:risks-assessed`)

Evaluate impact. Load modules/risk-assessment-framework.md for risk indicators, levels, and scoring methodology.

Step 4: Prepare Summary (`diff-analysis:summary-prepared`)

Synthesize findings: theme, scope with counts, risk level, review focus, dependencies. Format for downstream consumption (PR descriptions, release notes, reviews).

Exit Criteria

All TodoWrite items completed with categorized changes and risk assessment
Downstream workflows have semantic understanding of the changeset
Summary ready for appropriate consumption (review, release notes, planning)

---name: diff-analysisdescription: Methodology for categorizing changes, assessing risks, and creating summaries from any changeset. Triggers: diff analysis, changeset review, risk assessment, change categorization, semantic analysis, release preparation, change summary, git diff Use when: analyzing specific changesets, assessing risk of changes, preparing release notes, categorizing changes by type and impact DO NOT use when: quick context catchup - use catchup instead. DO NOT use when: full PR review - use review-core with pensive skills. Use this skill for systematic change analysis with risk scoring.---# Diff Analysis Methodology## OverviewStructured method for analyzing changesets: categorize changes, assess risks, generate insights. Works for git diffs, configuration changes, API migrations, schema updates, or document revisions.## When to Use- Extracting insights from raw change data- Categorizing and prioritizing changes before code reviews- Preparing release notes or changelogs- Assessing migration scope and risk## Activation Patterns**Trigger Keywords**: diff, changes, release notes, changelog, migration, impact, risk assessment**Auto-Load When**: Git diffs present, change analysis requested, impact assessment needed.## Progressive LoadingLoad modules based on workflow stage:### Always Load- `modules/semantic-categorization.md` for change categorization workflow### Conditional Loading- `modules/risk-assessment-framework.md` when risk assessment is needed- `modules/git-diff-patterns.md` when working with git repositories### Integration- Use `sanctum:git-workspace-review` for git data gathering- Use `imbue:evidence-logging` for capturing analysis evidence- Use `imbue:structured-output` for formatting final deliverables## Required TodoWrite Items1. `diff-analysis:baseline-established`2. `diff-analysis:changes-categorized`3. `diff-analysis:risks-assessed`4. `diff-analysis:summary-prepared`Mark each item complete as you finish the corresponding step.## 4-Step Methodology### Step 1: Establish Baseline (`diff-analysis:baseline-established`)Define comparison scope: what states are being compared, boundary of analysis, and scale metrics.For git contexts, load `modules/git-diff-patterns.md`. For other contexts, compare relevant artifacts.### Step 2: Categorize Changes (`diff-analysis:changes-categorized`)Group changes by semantic type. Load `modules/semantic-categorization.md` for change categories, semantic categories, and prioritization.### Step 3: Assess Risks (`diff-analysis:risks-assessed`)Evaluate impact. Load `modules/risk-assessment-framework.md` for risk indicators, levels, and scoring methodology.### Step 4: Prepare Summary (`diff-analysis:summary-prepared`)Synthesize findings: theme, scope with counts, risk level, review focus, dependencies. Format for downstream consumption (PR descriptions, release notes, reviews).## Exit Criteria- All TodoWrite items completed with categorized changes and risk assessment- Downstream workflows have semantic understanding of the changeset- Summary ready for appropriate consumption (review, release notes, planning)

Frequently asked questions