kin0992 Generate a PR title and description
Summarize a branch for reviewers with a concise PR title and markdown description.
Instructions
- Read commits, diff, and optional template before writing.
- Write a title: imperative mood, ≤72 chars, summarizing the primary user-facing change.
- If a PR template is provided, fill its sections. Otherwise use:
- Why – motivation or linked context
- What – concise bullets grouped by area
- How to verify – checks or tests for reviewers
- Risks / follow-ups – anything to watch closely Omit empty sections.
- Describe intent and outcome, not every edit. Never fabricate ticket numbers, links, or steps.
Output
Return only the title and description:
TITLE: <pr title>
<description in markdown>
Example
TITLE: Add retry handling for webhook delivery
## Why
Transient outages could permanently fail webhook delivery.
## What
- retry failed deliveries before marking them failed
- emit retry metrics
- document retry behavior
## How to verify
- review retry path tests
- confirm metrics for retries and terminal failures
Common edge cases
- If a template includes required headings, preserve them.
- If verification details are missing, do not invent steps.