What problem does it solve? Pull requests often ship with missing, thin, or jargon-heavy descriptions that slow down code review and leave future developers without useful context. This Skill turns a git diff, commit list, or rough notes into a complete, well-structured PR description that explains both what changed and why. ## Core Features & Use Cases - Structured PR Templates: Produces descriptions with Summary, Changes, Testing, Breaking Changes, and Related sections, including checkbox-style testing evidence. - Dual Tone Modes: Adapts output for internal reviewers or stakeholder-facing audiences, with an extended template covering migration guides, timelines, and business-value-first summaries. - Assumption Flagging: Ends each draft with a note listing gaps (missing ticket links, unconfirmed tests, unspecified breaking-change impact) so the author knows exactly what to fill in. - Use Case: After finishing a feature branch, paste your git log --oneline output and a one-line summary, and receive a review-ready PR body that flags the DB migration as a breaking change and prompts you to confirm integration test status. ## Quick Start Ask the assistant to write a PR description from your git diff or a short summary of what changed and why.
