diff-analysis

## 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) # 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 ## Re...