Agent skill · Code Review & Quality

diff-analysis

Use this skill for systematic change analysis with risk scoring. 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.'

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill diff-analysis-athola-claude-night-market-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Version: 1.4.0
Path: skills/analysis/diff-analysis-athola-claude-night-market-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Activation Patterns](#activation-patterns) - [4-Step Methodology](#4-step-methodology) - [Exit Criteria](#exit-criteria) - [Troubleshooting](#troubleshooting) # 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-assessme

What's inside
Steps it walks through
  1. Table of Contents
  2. Overview
  3. When To Use
  4. When NOT To Use
  5. Activation Patterns
  6. Progressive Loading
  7. Always Load
  8. Conditional Loading
  9. Integration
  10. Required TodoWrite Items
  11. 4-Step Methodology
  12. Step 1: Establish Baseline (diff-analysis:baseline-established)
  13. Step 2: Categorize Changes (diff-analysis:changes-categorized)
  14. Step 3: Assess Risks (diff-analysis:risks-assessed)
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the diff-analysis skill do?

Use this skill for systematic change analysis with risk scoring. 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.'

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill diff-analysis-athola-claude-night-market-2 --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.

Keep going