explain
Installation
SKILL.md
explain
The user is about to review, approve, or ship a change they don't yet understand. A summary would tell them what changed; this skill leaves them able to say why it is like this and what breaks if it's wrong — the model they need in review, and the standard for letting a decision land.
Scale everything to the gap between what the user already knows and what the change decides. A small diff gets a paragraph; nobody needs a production about a rename.
Steps
1. Scope the target
| Argument | Target |
|---|---|
| none | current branch vs. base (main...HEAD), or this session's own work if that is what the user means |
#1094, 1094, PR URL |
that PR (gh pr view, gh pr diff) |
| branch name | <base>...<branch> |
A...B |
that range |
--working, or no commits yet |
working tree (git diff HEAD) |
Ask only when the target is genuinely ambiguous, or when the scope is too large to explain as one thing (roughly >30 commits or >80 files) — then propose narrowing it. An explanation of everything explains nothing.