agentmods.dev

diff-analysis

diff-analysis is a skill for Claude Code from athola/claude-night-market. It costs 32 tokens per session (700 once invoked), scanned A, original, MIT.

A change-analysis method that examines diffs and other change sets, groups their meaning and impact, assesses risk, and prepares release notes. A diff is a record of what changed between two versions of code or documents.

In plain words
What is it for?
Use it to assess git diffs, configuration changes, API or database-schema migrations, document revisions, and changelogs.
Why use it?
It turns raw changes into a clearer view of what changed, what may be risky, and what should be communicated in a release.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the TodoWrite tool.

Part of the imbue plugin — 5 skills, 5 commands, 1 agent shipped together

not rated 342repo +1 today A scan 32 tokens original MIT

Good fit Use it to assess git diffs, configuration changes, API or database-schema migrations, document revisions, and changelogs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/athola/claude-night-market/diff-analysis
View source ↗ athola/claude-night-market athola.github.io
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add athola/claude-night-market --skill diff-analysis
Clone the repo
git clone --depth 1 https://github.com/athola/claude-night-market

Made for: Claude Code.

Or install imbue, the plugin that ships this one along with the rest of its 5 skills, 5 commands, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for diff-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/athola/claude-night-market/diff-analysis/github.svg)](https://agentmods.dev/skills/athola/claude-night-market/diff-analysis)
Your own site
<a href="https://agentmods.dev/skills/athola/claude-night-market/diff-analysis"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/diff-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for diff-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/athola/claude-night-market/diff-analysis"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/diff-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 700 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00700
Opus 5.5 $0.00013 $0.00280
Sonnet 5.5 $0.00006 $0.00140
Haiku 4.5 $0.00003 $0.00070

Measured 14d ago against content hash 5790d665edee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

diff-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 14d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/imbue/skills/diff-analysis/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Read the full file on GitHub · 92 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 14d ago First seen · 92 lines · 32 tokens per session scan A 5790d665edee

Subscribe to this mod's changes

diff-analysis is a skill published in the GitHub repository athola/claude-night-market (342 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 700 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-03.

Claude CodeCode reviewGit and workflowReleasesanalysis-methodsawesome-claude-codeawesome-claude-skillscategorizationchangesclaude-code-plugins-marketplaceclaude-commandsclaude-hooksrisk assessmentsemantic-analysissummaries
Related

Other skills, from other repositories

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

github

GitHub via gh CLI: PRs, issues, reviews, repos, auth.

NousResearch/hermes-agent · 19 tokens

release

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…

hyhmrright/brooks-lint · 135 tokens

ln-62-release-publisher

Prepares and publishes an explicitly requested tagged GitHub release; does not deploy applications.

levnikolaevich/claude-code-skills · 24 tokens

work-with-pr

Manage the full PR lifecycle using the github MCP: create, update, review, merge. Trigger when the user says 'create PR', 'update PR', 'review PR', 'merge PR', or needs to work with pull requests.

omagents/omagents · 51 tokens

release-habit-hooks

Cut a new release of the habit-hooks packages. Use when asked to release, publish, or bump the version. Reviews what lands, enforces the in-sync versioning rule, validates the changelog, and drives the tag-triggered PyPI publish.

habit-hooks/habit-hooks · 56 tokens