360 Secure SkillHub
360 安全技能中心

diff-analysis

面向变更集的结构化分析方法论：先确立对比基线，再按语义类型对 git diff、配置变更、API 迁移、schema 更新或文档修订进行分类，随后评估风险，最后汇总主题、范围、风险级别与评审重点，形成可用于评审或发布说明的摘要。

athola
athola
热度 62.01
最近更新 2026-08-26 21:13:43
分类：开发依赖：代码执行应用场景：代码审查 / 摘要总结 / 报告撰写 / 工作流

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add nm-imbue-diff-analysis
Metadata
name
diff-analysis
description
Analyzes changesets with risk scoring, categorization by type and impact, and release note preparation
version
1.9.8
triggers
["changes","semantic-analysis","risk-assessment","categorization","summaries","extracting insights from raw change data"]
metadata
{"openclaw":{"homepage":"https://github.com/athola/claude-night-market/tree/master/plugins/imbue","emoji":"🦞","requires":{"config":["night-market.imbue:proof-of-work"]}}}
source
claude-night-market
source_plugin
imbue

Night Market Skill — ported from claude-night-market/imbue. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Table of Contents

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)