commit-push-pr

Determine which branch you're on, then follow the appropriate flow. Do not add Co-Authored-By trailers or AI-generated footers to commits or PR descriptions.

Invocation Contract

Run this command only when the human explicitly invokes it (typed /commit-push-pr or one of the Trigger Phrases at the bottom of this file). Do not auto-launch from a "we're done" inference. The Version bump: AskUserQuestion at step 6 is mandatory and never auto-answerable — refuse to proceed without an explicit human selection. See CLAUDE.md Critical Rule 13.

Worktree Awareness

If you are in a git worktree session:

• Verify you are on the correct branch: git branch --show-current
• All changes must be committed before creating a PR — git status --porcelain should be empty after staging
• Do NOT attempt to switch branches inside a worktree — each worktree is locked to its branch

On a feature branch (feature/, fix/, chore/, refactor/)

Feature branches contain ONLY the task changes. Do NOT touch shared-state files (see git-conventions.md for the canonical list).

1. Stage all changes: git add -A
2. Write a clear, conventional commit message and create the commit.
3. Capture the new HEAD SHA: git rev-parse HEAD — this is the value to embed in the session summary's sha: line so the next /start can compute drift accurately (git log <sha>..HEAD).
4. Write a session summary to .claude/sessions/:
   • Filename: YYYY-MM-DD-HHMM-{short-branch-name}.md
   • Content format:

     # Session: {date}
     sha: {full HEAD SHA captured in step 3}
     **Branch:** {current branch}
     **Task:** {one-line summary of what was worked on}
     
     ## Completed
     - {what was done, 3-5 bullet points}
     
     ## Files Modified
     - {list key files changed, from git diff --name-only}
     
     ## Notes for Next Session
     - {anything the next session should know}
     
     ## Workflow Observability
     - **Agents invoked:** {ALL agents used this session — explicit @agent calls AND agents invoked implicitly by commands like /verify, /review-plan, /refactor-clean. Write "none" if no agents were used.}
     - **Commands used:** {all slash commands run earlier in this session, e.g. /start, /verify, /refactor-clean. Do NOT include the current /commit-push-pr or /end that is writing this summary. Write "none" if no other commands were used.}
     - **Verification result:** {if /verify was run: passed/failed with brief summary; otherwise "not run".}
     

   • The sha: line MUST be its own line starting with sha: (case- sensitive, no leading whitespace, no markdown formatting around it). /start parses it with grep -oP '^sha:\s*\K[a-f0-9]+'.
   • Keep it concise — this is for machine consumption at session start, not a detailed report.
   • The .claude/sessions/ directory is gitignored; do not stage it.
5. Push to the current branch.
6. Required: prompt for Version bump: declaration via AskUserQuestion. Use AskUserQuestion with these four options and one-line descriptions: