This skill MUST be used when drafting GitHub Pull Request or GitLab Merge Request titles and descriptions. This includes when the user asks to "create a PR", "open a PR", "raise a MR", "write a PR description", "draft a merge request", "submit a PR", "make a merge request", or when an agent workflow reaches a PR/MR creation step. This skill should also be used when reviewing or rewriting an existing PR/MR description.
Draft titles and descriptions for GitHub Pull Requests and GitLab Merge Requests by reading the actual changes from git, then presenting the draft for user confirmation before creating.
This skill takes precedence unless the current project's CLAUDE.md or equivalent defines its own PR/MR description process.
Auto-detect from git tracking info. Fall back to main, master, or develop (in that order, whichever exists). Accept an explicit override as an argument (e.g. /draft-pr develop).
Gather context from:
# All commits on this branch relative to base
git log --oneline <base>..HEAD
# Full diff against base
git diff <base>...HEAD
# Current branch name
git rev-parse --abbrev-ref HEAD
Read all commits, not just the latest. The description must reflect the entire branch.
Default format (overridable by project CLAUDE.md):