ship

Ship Changes

Automates the full flow: branch creation (if needed), commit, push, and PR creation with a concise description.

---

Important Rules

• BLOCKING: NEVER add Co-Authored-By lines or Claude attribution to commits or PR descriptions
• BLOCKING: NEVER mention that the PR description was generated by an AI or assistant
• Write all commit messages and PR descriptions as if the user wrote them
• Use imperative mood for commit messages
• Keep PR descriptions concise and focused on the "why"

---

Phase 1: Assess Current State

Run these commands in parallel:

git status
git diff --stat
git diff --staged --stat
git log --oneline -5
git rev-parse --abbrev-ref HEAD

Determine:

• Current branch: Are we on the base branch (main/master/develop)?
• Changes: What files are modified, staged, or untracked?
• If no changes exist: Inform the user and stop.

---

Phase 2: Create Branch (if on base branch)

If current branch is main, master, or develop:

1. Analyze the changes to generate a short, descriptive branch name
2. Use format: <type>/<short-description> (e.g. fix/search-pagination, feat/match-scoring)
3. Present the branch name to the user for confirmation using AskUserQuestion
4. Create and switch to the branch:

   git checkout -b <branch-name>
   

If already on a feature branch, skip this phase.

---

Phase 3: Commit Changes

1. Review git diff (staged and unstaged) to understand all modifications
2. Group related changes logically — prefer one commit unless changes are clearly separate concerns
3. Stage files with specific paths (never use git add -A or git add .)
4. Draft clear commit message(s):
   • Imperative mood ("Add feature" not "Added feature")
   • Focus on why, not just what
   • First line under 72 characters
5. Create the commit(s) — do NOT add any Co-Authored-By lines
6. Verify with git log --oneline -3

If $ARGUMENTS includes a commit message hint, use it as guidance.