pr-push

PR Push Skill

You are entering the PR push phase. You will create or update a draft PR, automatically fixing any pre-commit hook failures until the push succeeds.

CRITICAL SAFETY RULE: This skill MUST NEVER publish a PR. Always use --draft flag.

Process

Step 1: Pre-flight Checks

Run checks 1-5 in parallel where possible.

1. Check current branch:

   git branch --show-current
   

   • If on main: Ask user what branch name to use, then create the branch using the detected stack workflow from Step 1.4
   • Otherwise: Continue with current branch

2. Check if PR already exists (run early — gates later steps):

   gh pr view --json number,state,isDraft,url,title,body,baseRefName 2>/dev/null
   

   • If PR exists: Record PR number, URL, current body, and current base branch. Skip Step 2 (metadata generation) and skip stack submission or git push if remote is already up-to-date. Proceed to update description if needed.
   • If no PR: Will create new draft PR — continue to Step 2.

3. Check for uncommitted changes:

   git status --porcelain
   

   • If there are uncommitted changes: Warn user and ask if they should be committed first

4. Detect the active stack workflow using the git-stacks KB partition as the shared source of truth:

   • list_kb_documents for partition git-stacks
   • read_kb_document_by_path for /index.md
   • Run the dedicated-client checks from git-stacks/index.md
   • If a dedicated client is detected, record STACK_CLIENT accordingly
   • If no dedicated client is detected, inspect GitHub base refs and local branch relationships to decide whether this is a native git stack
   • Load the matching KB client doc (/charcoal.md, /git-town.md, or /native-git.md) before pushing or navigating the stack
   • If no stack is confirmed: Use standard git workflow (Step 3b)

5. Resolve the target PR base from local branch relationships:

   git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null
   git log --pretty=format:'%D' | grep -v '^$' | grep -v "^HEAD -> $(git branch --show-current)$" | head -1 | tr ',' '\n' | sed 's/^ *//' | grep -v "HEAD" | grep -v "origin/HEAD" | head -1
   

   • Prefer the detected stack client's local parent metadata when it is available
   • Otherwise, use the git upstream/tracking branch and normalize remote refs like origin/feature/foo to feature/foo
   • Otherwise, fall back to the existing local parent-branch heuristic
   • If multiple sources disagree, or no unambiguous base can be determined, STOP and ask the user
   • Record the resolved branch as TARGET_BASE
   • Never silently fall back to the repository default branch