pr

Create Pull Request

Create a pull request for the current branch, following commit message rules for the title (important for squash-merge).

PR Title Rules

The PR title becomes the commit message when squash-merging. Follow these rules:

1. Limit to 50 characters (hard limit for commit subjects)
2. Capitalize the first word
3. No period at the end
4. Use imperative mood ("Add", "Fix", "Update" — not "Added", "Fixed")
5. Explain what, not how

Good Examples

• Add validation for email format
• Fix login timeout on slow connections
• Update dependencies to patch security issue

Bad Examples

• Fixed the bug (past tense, vague)
• Updates to the login page. (third person, period, vague)
• WIP: trying to fix auth (WIP, lowercase, vague)

PR Body

Include:

• Summary: 1-3 bullet points of what changed and why
• Test plan: How to verify the changes work

Process

1. Commit hygiene check — before anything else, scan for fixup commits:

   git log --oneline $(git merge-base HEAD main)..HEAD
   

   If any commit messages match these patterns (case-insensitive), invoke scm-tools:cleanup-commits before proceeding:
   • fixup! or squash!
   • WIP
   • address review or review feedback
   • lint, rubocop, typo as standalone fixes
2. Check current branch status and commits since diverging from base
3. Determine base branch (use argument if provided, otherwise main)
4. Push branch to remote if needed
5. Create PR with properly formatted title and body using gh pr create
6. Return the PR URL