Create Pull Request

Streamlined workflow to commit, branch, push, and create a PR in one command.

Your Task

1. •Check git status and diff to see what changes exist (staged, unstaged, untracked)
2. •Check git log to understand recent commit message style
3. •Identify relevant changes: Only include files and changes from the current conversation context. Ignore pre-existing uncommitted changes that are unrelated to the current task.
4. •Determine if there's an associated issue:
   • •Check the conversation context for any GitHub issue references (#123, issue URL, etc.)
   • •If found, note the issue number for the PR body
   • •If not found and changes suggest an issue context, ask the user
5. •Create a new branch from main:
   • •If already on main, create the branch directly: git checkout -b <branch-name>
   • •If on a different branch with uncommitted changes, use a git worktree to avoid disrupting the current branch:
     1. •git worktree add ../<repo>-pr-<branch-name> main (create worktree from main)
     2. •cd ../<repo>-pr-<branch-name>
     3. •git checkout -b <branch-name>
     4. •Copy only the relevant changed files from the original worktree
   • •If on a different branch with no uncommitted changes, git checkout main && git checkout -b <branch-name>
6. •Stage and commit only the relevant changes with a descriptive commit message following the repo's style
7. •Push the branch to origin with -u flag
8. •Create the PR using gh pr create --base main
9. •Clean up worktree if one was created: go back to original directory and git worktree remove ../<repo>-pr-<branch-name>

PR Body Format

If there's an associated issue, the PR body MUST start with Closes #X:

Closes #123

## Summary
- Bullet points describing the changes

## Test plan
- [ ] Test steps

🤖 Generated with [Claude Code](https://claude.com/claude-code)

If there's NO associated issue, omit the Closes line:

## Summary
- Bullet points describing the changes

## Test plan
- [ ] Test steps

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Branch Naming

Use conventional prefixes:

• •fix/ - Bug fixes
• •feat/ - New features
• •chore/ - Maintenance, CI, tooling
• •refactor/ - Code refactoring
• •docs/ - Documentation changes

Keep branch names short and descriptive (e.g., fix/idempotent-mobile-build).

Commit Message Format

Follow the repository's existing commit style. Generally use conventional commits:

• •fix: description for bug fixes
• •feat: description for new features
• •chore: description for maintenance

Always append:

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Important

• •Always check git status and git diff before committing
• •Never commit sensitive files (.env, credentials, etc.)
• •Stage specific files rather than using git add -A
• •Always target main as the PR base branch
• •Only include changes from the current conversation context — do not pull in unrelated uncommitted work
• •Return the PR URL at the end so the user can access it