Skip to content
cccskills
FreePublished on GitHub

diff-analysis

Analyzes changesets with risk scoring, categorization by type and impact, and release note preparation. Use when extracting insights from raw change data.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md3.2 KB
  • modules/git-diff-patterns.md1.6 KB
  • modules/risk-assessment-framework.md3.1 KB
  • modules/semantic-categorization.md2.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Shapes turns action-first: action leads, steps numbered, state restated. Use for ADHD-friendly output. Do not use to trim tokens; use response-compression.

The English summary is being prepared. Showing the original description.

athola/claude-night-market342Updated Oct 17, 2026

Inverts burden of proof for code additions. Use when reviewing PRs, planning refactors, or running unbloat to challenge every addition's necessity.

The English summary is being prepared. Showing the original description.

athola/claude-night-market342Updated Oct 17, 2026

Tracks per-agent token usage and flags waste in parallel dispatch. Use when evaluating parallel agent efficiency or after a multi-agent run.

The English summary is being prepared. Showing the original description.

athola/claude-night-market342Updated Oct 17, 2026

Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.

The English summary is being prepared. Showing the original description.

athola/claude-night-market342Updated Oct 17, 2026

Evaluates API surface design, consistency, and exemplar alignment. Use when reviewing public API changes or before releasing a new API surface.

The English summary is being prepared. Showing the original description.

athola/claude-night-market342Updated Oct 17, 2026

Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.

The English summary is being prepared. Showing the original description.

athola/claude-night-market342Updated Oct 17, 2026

See all skills by athola

Report a problem with this skill