athola/diff-analysis
plugins/imbue/skills/diff-analysis/SKILL.md
Analyzes changesets with risk scoring, categorization by type and impact, and release note preparation. Use when extracting insights from raw change data.
$ install --global
skillsauthnpx skillsauth add athola/claude-night-market diff-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 27, 2026, 4:42 AM115.0s4 files scanned
SKILL.md
- name:
- diff-analysis
- description:
- Analyzes changesets with risk scoring, categorization by type and impact, and release note preparation. Use when extracting insights from raw change data.
- alwaysApply:
- false
- category:
- analysis-methods
- - imbue:
- proof-of-work
- tools:
- []
- complexity:
- intermediate
- model_hint:
- standard
- progressive_loading:
- true
- module_strategy:
- workflow-based
- estimated_tokens:
- 800
Table of Contents
- Overview
- When to Use
- Activation Patterns
- 4-Step Methodology
- 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.mdfor change categorization workflow
Conditional Loading
modules/risk-assessment-framework.mdwhen risk assessment is neededmodules/git-diff-patterns.mdwhen working with git repositories
Integration
- Use
sanctum:git-workspace-reviewfor git data gathering - Use
imbue:proof-of-workfor capturing analysis evidence - Use
imbue:structured-outputfor formatting final deliverables
Required TodoWrite Items
diff-analysis:baseline-establisheddiff-analysis:changes-categorizeddiff-analysis:risks-assesseddiff-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)
Related Skills
athola/ideate
research
VerifiedTrustedCommunity
Generate diverse solution candidates with category-spanning ideation methods and rotation. Use when stuck on a design or fighting repetitive LLM output.
304SKILL.mdUpdated Jun 8, 2026
athola/plugins/sanctum/skills/validate-pr
tools
VerifiedTrustedCommunity
--- name: validate-pr description: Use when you need a diff-derived test plan for a PR: reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions. alwaysApply: false category: validation tags: - pr - validation - test-plan - diff - revert-test - evidence tools: [] usage_patterns: - diff-derived-test-plan - revert-test-quality-check - evidence-capture complexity: intermediate model_hint: standard estimated_tokens: 650
304SKILL.mdUpdated Jun 8, 2026
athola/decision-journal
development
VerifiedTrustedCommunity
Contract for the project decision journal (tradeoffs and lessons-learned logs). Use when recording a decision, tradeoff, or lesson, or building a consumer hook.
304SKILL.mdUpdated Jun 8, 2026
athola/graduated-implementation
development
VerifiedTrustedCommunity
Ramps implementation ambition a notch only after the prior increment is understood. Use when building a feature you must understand, not just ship.
304SKILL.mdUpdated Jun 8, 2026