Git Pull Request Creation

Create focused, minimal pull requests that respect repo conventions. The PR title is the permanent record — it becomes the squash-merge commit on the default branch.

References (read when needed):

• references/worked-example.md — read when composing multi-commit PR descriptions

PR Size: Check Before You Compose

Before writing a single word of the description, assess whether the PR is the right size. A reviewer can hold a 200-line change in their head during a focused 30-60 minute session. A 2000-line change they cannot — they'll skim, miss things, and the review will be shallow.

Signs a PR is too large:

• More than ~400 lines changed (additions + deletions)
• More than ~8 files touched across unrelated concerns
• The title requires "and" to capture what it does
• You'd need more than a paragraph to explain what's in it

These are guidelines, not hard cutoffs — a 450-line change touching one well-understood module may be fine; a 300-line change spanning 12 unrelated concerns may not be.