What problem does it solve? Pull request copy often narrates implementation details instead of explaining the motivation behind a change, forcing reviewers to reverse-engineer intent from the diff. This Skill produces titles and descriptions grounded in the why — the user pain, business need, or outcome — rather than what files changed. ## Core Features & Use Cases - Why-focused titles: Generates one imperative sentence under 72 characters describing the motivation or outcome, not the mechanism. - SAR-structured descriptions: Writes Situation, Action, Result sections that explain the problem, the intent-level approach, and the observable result. - Automatic context gathering: Runs git diff main...HEAD --stat and git log main...HEAD --oneline to infer intent when no summary is provided, asking one focused question only when the why is genuinely ambiguous. - Use Case: You finished a branch fixing silent logouts from expiring auth tokens. Instead of writing "Refactor token refresh logic", the Skill produces "Fix silent logout when auth token expires" with a description explaining the user impact. ## Quick Start Ask the assistant to write the PR title and description for your current branch, optionally pasting a diff or a short summary of the change.
