Menu

Individual skill

explain-diff

Explain a code change, its reasons, effects, trade-offs, and verification limits.

plugins/reidemeister94/development-skills/skills/explain-diff/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,537
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Explain diff

Explain the change so the user can understand its behavior and maintain it.
Manual mode is repository-read-only; `--visual` may write only to system temp.

Use the requested worktree, branch, range, pull request, patch, or packet. Default to the current worktree.
Inspect the implementation, request, relevant decisions, verification, review verdict, and evidence limits.
Use runtime data and logs when they settle a material claim. Label absent or stale evidence **Unverified change**.
For `--visual`, read [visual mode](references/visual-mode.md).

Explain the result, prior behavior, reasons, important failure cases, operational effects, and trade-offs.
The explanation must stand alone without requiring the user to open the repository.
Explain public or operational names before using them. Include implementation detail only when it helps the user's purpose.
Use a diagram or concrete example when it makes the behavior clearer.