Pr Description

Process

1. Run git log main..HEAD --oneline (or appropriate base branch) to see the commits
2. Read the repo's PR template if available (.github/pull_request_template.md)
3. Optionally ask the user for a branch name suggestion too

Writing Style

• Keep it concise — match depth to the scope of the change
• Adapt or omit template sections to fit the PR; don't fill in sections that add no value
• Don't repeat what's already obvious from commit messages — reference them instead
• Use backticks for file and symbol references — no file hyperlinks (e.g. VS Code markdown links)
• No subjective claims about quality or efficiency
• No line-wrapping / hard-wrapping — let text flow naturally

Formatting

• Present the entire PR description inside a single fenced code block for easy copy-paste
• If the PR has well-scoped commits that tell a clear story, suggest reviewing one commit at a time in the Reviewer Notes