diff-analysis
Methodology for categorizing changes, assessing risks, and creating summaries from any changeset. 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.
npx skills add majiayu000/claude-skill-registry --skill diff-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 1. `diff
- Overview
- When to Use
- Activation Patterns
- Progressive Loading
- Always Load
- Conditional Loading
- Integration
- Required TodoWrite Items
- 4-Step Methodology
- Step 1: Establish Baseline (diff-analysis:baseline-established)
- Step 2: Categorize Changes (diff-analysis:changes-categorized)
- Step 3: Assess Risks (diff-analysis:risks-assessed)
- Step 4: Prepare Summary (diff-analysis:summary-prepared)
- Exit Criteria
What does the diff-analysis skill do?
Methodology for categorizing changes, assessing risks, and creating summaries from any changeset. 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.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill diff-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.