explain-changes
Installation
SKILL.md
Explain Changes
Build a grounded explanation of a change: the problem or previous state, the new behavior, and its practical effect on users, callers, or maintainers. Deliver it in the conversation, respecting the user's language and technical background. Scale the explanation to the substance of the change.
Establish the comparison
Use the target already identified in the conversation. When none is identified, inspect the working tree first. If it contains changes, explain those; otherwise ask which PR, commit, branch, version, or patch the user means. Ask when multiple plausible targets would lead to materially different explanations.
State the scope and baseline briefly so the reader knows what is being compared: