PR Creation Patterns

Claude Code can create pull requests through the gh CLI — title, description, labels, reviewers, and all. The quality of the PR it creates depends entirely on the context it has accumulated during the session. A session where Claude wrote the code, ran the tests, and fixed the errors produces a PR description that accurately summarizes what changed, why it changed, and what was tested. A cold session that just runs "create a PR for the current branch" produces a generic description that helps no one.

The pattern is: build context first, create PR last. Let Claude do the work — or at minimum, let it review the diff — before asking it to create the PR. The prompt "Review the changes on this branch and create a PR with a detailed description" produces dramatically better results than "Create a PR for this branch."

## Pull Requests
- Always include a Summary section with bullet points of what changed
- Always include a Test Plan section describing how to verify
- Link related issues using "Closes #123" syntax
- Request review from the appropriate team based on files changed
- PR title: conventional commit format, under 72 characters