pr

Open Pull Request

Introduction

Handle the full workflow from current branch state to an open, CI-monitored pull request. This command enforces branch discipline, analyzes all branch changes for a business-value-focused description, ensures documentation is current, and requires user approval at every step.

Arguments

#$ARGUMENTS

Supported arguments:

• commit — Stage, commit, and push uncommitted changes before proceeding. Without this argument, no commits are made — the command works only with what is already committed on the branch.

Main Tasks

1. Safety Checks & Branch Setup

• Verify we are NOT on stable or main:

  git branch --show-current
  

  If on a protected branch, stop immediately and inform the user.
• Check working tree status:

  git status --short
  

  If there are uncommitted changes and commit was NOT passed, warn the user but do not commit.
• Ensure the branch tracks a remote:

  git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null || echo "no upstream"
  

  If no upstream, set one:

  git push -u origin $(git branch --show-current)
  

2. Commit Changes (only when commit argument is provided)

Skip this phase entirely if commit was NOT passed as an argument.

When commit IS provided:

1. Run the required quality gates:

   uv run pre-commit run
   

   Fix any issues that arise before committing.
2. Stage all changes:

   git add -A
   

3. Create a commit with a descriptive message following project conventions.
4. Push to remote:

   git push
   

3. Analyze All Branch Changes

1. Find the merge base with stable:

   git merge-base stable HEAD
   

2. Review all commits on this branch:

   git log stable..HEAD --oneline
   

3. Review the full diff:

   git diff stable...HEAD --stat
   

4. Read changed files to understand the full scope of changes.
5. Check if a spec exists for this work (look in .specify/ or specs/).