Pr Title Description

Generate a PR title and description

Summarize a branch for reviewers with a concise PR title and markdown description.

Instructions

1. Read commits, diff, and optional template before writing.
2. Write a title: imperative mood, ≤72 chars, summarizing the

primary user-facing change.

1. 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.

1. Describe intent and outcome, not every edit. Never fabricate ticket

numbers, links, or steps.

Output

Return only the title and description:

TITLE: 

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: kin0992
• Source: kin0992/dev-toolkit
• License: MIT

Install and usage instructions live in the source repository linked above.