explain-pr
Explain PR — explain a PR/MR in plain language
Turn a freshly created Pull Request / Merge Request into a clear, friendly explanation the user can read in one pass to understand what changed, why it was done, and how it works — with the relevant code shown inline.
This replaces the manual prompt a user would otherwise type ("explain what you did, why, and how, in simple terms, with the relevant code"). The point is that the user shouldn't have to ask: once a PR/MR exists, they almost always want this recap.
When to use this skill
Trigger it on your own, without waiting to be asked, right after a PR/MR is created or finished — that's the moment the user wants the recap. Concretely:
- Just after
gh pr create,glab mr create, or opening a PR/MR through any other means. - When the user says things like "explain the PR", "what did you change?", "walk me through this MR", "recap the changes" — in any language.
If you just finished a PR/MR in this same conversation, you already did the work — you know most of the why firsthand. Use that, but still anchor the what and how in the real diff (see below) so nothing is misremembered or invented.