mcpField
D
diff-analysis

diff-analysis

github.com/atholaDevelopment343102 installsUpdated 1d ago
Repository

About diff-analysis

A structured change-analysis skill for developers and reviewers working with diffs, configuration changes, migrations, or document revisions. It establishes a baseline, categorizes changes, assesses risk, and prepares a summary for review, release notes, or planning.

Key features

  1. 01Establishing comparison scope
  2. 02Semantic change categorization
  3. 03Risk assessment
  4. 04Summary preparation for downstream use
  5. 05Progress tracking across analysis steps

Use cases

  1. 01Prioritizing changes before code review
  2. 02Preparing release notes or changelogs
  3. 03Assessing migration scope and risk
  4. 04Analyzing configuration or document revisions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/athola/claude-night-market --skill diff-analysis

After installing, type/diff-analysisin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

modules/
git-diff-patterns.md
risk-assessment-framework.md
semantic-categorization.md

Details

From the project README

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

When NOT To Use

  • Quick context catchup - use catchup instead
  • Full PR review - use review-core with pensive skills

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:proof-of-work for capturing analysis evidence
  • Use imbue:structured-output for formatting final deliverables

Required Progress Items

  1. 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 diff-analysis: progress items are marked complete
  • Every change is assigned a category and a risk level
  • The summary names its baseline and the intended consumer: review, release notes, or planning

Comments

Markdown supported