# Pull Request Checklist

## Framing

- State the problem, not only the code diff.
- Summarize the user-visible behavior change in one sentence.
- Separate implementation detail from reviewer guidance.

## Reviewability

- Point reviewers to the highest-risk files first.
- Document tests run, gaps, and remaining risks.
- Include migration or rollback notes when applicable.

## Merge Readiness

- Ensure titles are action-oriented and searchable.
- Avoid hiding follow-up work inside vague TODO language.
- Keep the description useful even when viewed outside the code host UI.