Generate Pull Request Description

Generate a short, narrative PR description that tells reviewers why this change exists and what to expect when they open the diff. Reviewers skim. If the description is long, they skip it. Respect their time.

Length budget — the hard rule

A reviewer should read the entire description in under 30 seconds. Concretely:

• Body target: ≤ 25 rendered lines. Hard ceiling: 40. Tables, checklists, and blank lines all count toward this.
• Why: 1–2 sentences. Not paragraphs.
• What changed: 2–4 bullets, one line each. No sub-bullets, no code blocks inside bullets.
• How to verify: ≤ 3 lines. Prefer a single command over prose.
• Notes for reviewers: optional. If present, ≤ 2 sentences. Move implementation detail into code comments or PR review threads, not the body.

If you can't fit the change inside this budget, the PR is probably too big — flag that to the user instead of expanding the description.

Core Principles

1. Narrative over checklist. Reads like prose explaining a decision, not a bullet-point manifest of every file touched.