PR

Create a pull request for the current branch against main.

Conventions

• Title: Conventional Commit format (type(scope): description), under 60 chars, no trailing period
• Body: follow .github/pull_request_template.md if it exists — fill in each section, do not add or remove sections
• Bullets: plain English, describe what changed and why — no code blocks, no prose paragraphs
• If an issue matches the branch work, add Fixes #<number> at the end of the body

Workflow

1. Check preconditions (all must pass before continuing):
   • working directory is clean (git status)
   • branch has commits ahead of main (git log main..HEAD --oneline)
   • project verification passes (run the project's test/lint/typecheck command)
2. Run the review skill (if available):
   • if there are must-fix findings, stop and report them — do not create the PR
3. Gather context:
   • read .github/pull_request_template.md if it exists
   • run git log main..HEAD --oneline to see commits
   • run git diff main...HEAD --stat to see changed files
   • run git diff main...HEAD to read the full diff
   • run gh issue list to check for an associated issue
4. Draft the PR:
   • infer a title from the commits and diff
   • fill in the template body (or use a sensible default structure)
5. Push if needed:
   • check remote tracking: git status -sb
   • if not pushed: git push -u origin HEAD
6. Create the PR:
   • gh pr create --title "..." --body "..."
7. Return only the PR URL

Rules

• Never create a PR with uncommitted changes in the working directory
• Never create a PR without running verification first
• Never create a PR with must-fix review findings
• Never push without checking remote tracking status first
• Always check for associated issues

See also

• review for severity and gating decisions
• docs for user-facing drift checks before merge
• sdd when the change depends on version-specific APIs

Red flags

• Skipping verification because "tests passed earlier"
• Skipping the review because it takes time
• Pushing before checking if the branch already tracks a remote
• Creating the PR without checking for associated issues