Get the FREE Ultimate OpenClaw Setup Guide →

diff-analysis

analysis-methods
npx machina-cli add skill athola/claude-night-market/diff-analysis --openclaw
Files (1)
SKILL.md
3.8 KB

Table of 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

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

Required TodoWrite 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 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)

Troubleshooting

Common Issues

Command not found Ensure all dependencies are installed and in PATH

Permission errors Check file permissions and run with appropriate privileges

Unexpected behavior Enable verbose logging with --verbose flag

Source

git clone https://github.com/athola/claude-night-market/blob/master/plugins/imbue/skills/diff-analysis/SKILL.mdView on GitHub

Overview

Diff analysis provides a structured method to examine changesets, categorize changes by type, and score risks to inform reviews and release notes. It covers git diffs, configuration changes, API migrations, schema updates, and document revisions.

How This Skill Works

The workflow follows four steps: establish baseline, categorize changes by semantic type, assess risks with a scoring framework, and prepare a downstream summary. It integrates with modules for git-diff patterns, semantic categorization, and risk assessment, and uses sanctum:git-workspace-review and imbue:evidence-logging to produce structured outputs.

When to Use It

  • Extracting insights from raw change data
  • Categorizing and prioritizing changes before code reviews
  • Preparing release notes or changelogs
  • Assessing migration scope and risk for schema or API changes
  • Planning downstream work using a structured summary for PRs

Quick Start

  1. Step 1: Establish Baseline (define scope and affected states)
  2. Step 2: Categorize Changes (group by semantic type using the recommended module)
  3. Step 3: Assess Risks and Prepare Summary (score impacts and craft downstream deliverables)

Best Practices

  • Define the comparison scope and baseline up front
  • Always load the semantic categorization module for change categorization
  • Conditionally load the risk assessment and git-diff pattern modules when needed
  • Apply consistent risk indicators and a transparent scoring method
  • Produce a downstream-ready summary and track TodoWrite items as you proceed

Example Use Cases

  • Evaluating a git diffset for a major feature release
  • Analyzing a configuration change rollout across environments
  • Assessing a database schema migration for risk and impact
  • Generating a changelog entry from a set of commits
  • Preparing a PR description focused on risks and dependencies

Frequently Asked Questions

Add this skill to your agents

Related Skills

catchup

athola/claude-night-market

'Use this skill to quickly understand "what changed and what matters".

Sponsor this space

Reach thousands of developers ↗