pr

PR Workflow Skill

Create a new branch from main, stage all changes, commit, push, create a PR, and iteratively fix all failing checks until they pass.

Arguments

• $ARGUMENTS - Branch name (required) and optional commit message
  • Format: <branch-name> [commit message in quotes]
  • Example: feat/add-auth "Add user authentication"

Philosophy: Ask Early, Ask Often

This skill should liberally use AskUserQuestion at every decision point. PRs are visible to the team — assumptions about commit messages, PR descriptions, and fix strategies should be validated. Specifically:

• Before committing — confirm commit message and staged files
• Before creating the PR — confirm title and description
• When checks fail — ask how to handle before auto-fixing
• After completion — ask about next steps

Workflow

1. Parse Arguments

Extract branch name and commit message from $ARGUMENTS:

• First word is the branch name
• Remaining text (if any) is the commit message
• If no commit message provided, generate one based on staged changes

2. Verify Clean State & Create Branch

# Fetch latest from origin
git fetch origin

# Create and checkout new branch from main
git checkout -b <branch-name> origin/main

3. Stage and Commit Changes

# Check what files have changes
git status

# Stage all changes
git add -A

# If no commit message provided, analyze changes for a message
git diff --cached --stat

3a. Confirm What Gets Committed

Before staging, present the changes and ask the user to confirm:

AskUserQuestion:
  question: "These files will be staged and committed. Does this look right?"
  header: "Stage"
  multiSelect: false
  options:
    - label: "Stage all changes"
      description: "<N files changed, +X/-Y lines — summary of key changes>"
    - label: "Let me pick files"
      description: "I want to selectively stage specific files"
    - label: "Review changes first"
      description: "Show me the diff before I decide"