</action>

<abort-if>
- On `main` branch (must be on a feature/fix branch)
- Typecheck fails
- No changes to commit (nothing to ship)
</abort-if>

<ask-user>
If the branch name doesn't match a clear issue or feature, ask:
- What is this change about? (for commit message)
</ask-user>
</phase>

<phase name="version-bump">
### Phase 2: Version Bump

Bump the development version using the format: `v{MAJOR}.{MINOR}.{PATCH}-dev-{YYYYMMDD}-{letter}`

<version-format>
| Component | Description |
|-----------|-------------|
| `MAJOR.MINOR.PATCH` | Semantic version (stays same during dev) |
| `YYYYMMDD` | Today's date |
| `letter` | Sequential letter for same-day releases: a, b, c... |

**Auto-increment logic**:
1. Read current version from `VERSION` file
2. If date matches today, increment the letter (a -> b -> c...)
3. If date is older, reset to today's date with letter `a`
</version-format>

<action>
1. Read `VERSION` file
2. Calculate next version
3. Update `VERSION` file with new version string
4. Sync to `package.json`:
   ```bash
   # Strip leading 'v' for npm (package.json uses bare semver)
   npm version "<version-without-v>" --no-git-tag-version --allow-same-version

</action>

<important>
- Stage files explicitly by name — never `git add -A` or `git add .`
- Never commit `.env`, credentials, or secrets
- Always include `Co-Authored-By` trailer
- Use HEREDOC for commit message formatting
- **Include all local changes**: If `/ship` discovers additional uncommitted changes on the branch (e.g., new skills, doc updates, config changes), include them in the commit and PR. Don't cherry-pick only the "primary" fix — ship everything on the branch together.
</important>
</phase>

<phase name="push-and-pr">
### Phase 5: Push and Create PR

Push the branch and open a pull request.

<action>
```bash
# Push with upstream tracking
git push -u origin <branch-name>

# Create PR with squash-friendly format
gh pr create --title "<type>: <short description>" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points of what changed and why>

## Files changed
<grouped list of changed files>

## Test plan
- [ ] `npm run typecheck` passes
- [ ] `npm run build` succeeds
- [ ] <domain-specific checks>

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

</action>

<important>
- This repo does NOT allow merge commits — always use `--squash`
- `gh pr merge --delete-branch` automatically deletes the remote branch
- If merge fails due to conflicts, abort and notify the user
</important>
</phase>

<phase name="cleanup">
### Phase 7: Switch to Main and Clean Up

Return to main branch with latest changes. Handle the case where `gh pr merge` already switched branches.

<action>
```bash
# Switch to main (may already be on main after gh pr merge)
git checkout main

# Pull latest (includes the squash-merged commit)
git pull

# Delete local branch (may already be deleted by gh pr merge)
git branch -d <branch-name> 2>/dev/null || true

# Verify clean state
git status
git log --oneline -3

</commands>

---

## Troubleshooting

<troubleshooting>
| Issue | Solution |
|-------|----------|
| `gh pr merge` fails with merge commit error | Use `--squash` flag (this repo requires it) |
| Branch already deleted | `git branch -d` will say "not found" — safe to ignore |
| PR has conflicts | Pull main into branch, resolve conflicts, push, then merge |
| Typecheck fails | Fix type errors before committing — never ship broken code |
| Build fails | Fix the build before committing — never ship broken code |
| VERSION and package.json out of sync | Update VERSION, then run `npm version` with `--no-git-tag-version` |
| `gh` not authenticated | Run `gh auth login` |
</troubleshooting>