PR Description

Draft pull request title and description from the current branch and diff so reviewers get context quickly.

When to Activate

• User is about to open a PR or asks for "PR description", "draft my PR", or "what should I write in the PR"
• Preparing a merge request for review
• After completing a feature and before requesting review

Work Process

1. Gather inputs — Branch name, base branch (e.g. main), and diff (git diff base..head or staged + unstaged). Optional: ticket/issue id from branch or commits.
2. Summarize the change — What is the main outcome? One logical change per PR. If the diff mixes unrelated work, note it and suggest splitting or summarize the dominant change.
3. Draft title — Short, imperative, ~50 chars. Optionally include ticket id if the project does (e.g. [PROJ-123] Add CSV export).
4. Draft description — Fill project template if one exists; otherwise use the structure below. What, how, testing, related links. Be specific; derive from diff, do not invent.
5. Check project template — If .github/PULL_REQUEST_TEMPLATE.md or similar exists, use its sections and checklist; add content to each.

Inputs