fastapi-pr

## Branch Run `git branch --show-current` and use its output. ## Commit history vs base Run `git log master..HEAD --oneline` and use its output. ## Files changed Run `git diff master...HEAD --stat` and use its output. ## Instructions Generate a PR description for the changes summarized above. Extract any ticket reference (e.g. FEAT-1234) from the branch name. Read CLAUDE.md for project conventions and any PR template rules. For key changed files, read them to understand the full context — do not paraphrase from the diff alone. Output format: ```markdown ## Summary <!-- 1-3 sentences explaining what this PR does and why --> ## Changes <!-- Bullet list of key changes, grouped logically --> ## Test Plan <!-- How the changes were tested --> - [ ] Tests pass locally - [ ] Manually verified ## Notes <!-- Anything reviewers should pay attention to, migration steps, feature flags, etc. --> ``` Rules: - **Write for a reviewer who has 30 seconds.** Lead with what changed and why it matters; surface the one thing they must look at. The Summary should orient them before they open a single file. - **Don't echo the diff.** The reviewer can read the diff. Summarize intent and group related changes — do not narrate every edit line by line. - **Describe the current end state, not a changelog.** Write what the PR *is*, not a chronological story of how you got there ("first I tried X, then changed to Y"). If you revised an approach mid-branch, describe only the final shape. - B...