| name | ship |
| description | Build, commit, push & version bump workflow. Use when you want to ship current changes — runs build verification (cargo), stages, commits with conventional message, bumps version optionally, and pushes. |
| allowed-tools | Read, Write, Edit, Bash, Grep, Glob |
| effort | low |
| tags | ["workflow","git","automation","release"] |
/ship - Build, Commit, Push & Version Bump
Automates the complete ship workflow for ccboard:
Workflow Steps
-
Build Verification
- Run
cargo build --all to ensure compilation succeeds
- Run
cargo clippy --all-targets to catch warnings
- Run
cargo test --all to verify tests pass
- If any step fails, stop and report errors
-
Stage Changes
- Run
git status to show current state
- Stage all changes with
git add -A
- Show what will be committed with
git diff --cached --stat
-
Commit
- Write a conventional commit message based on the changes:
feat: for new features
fix: for bug fixes
refactor: for refactoring
docs: for documentation
chore: for maintenance
- Commit format:
<type>: <description>
- Add Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com
-
Version Bump (optional)
- Check if Cargo.toml version needs bumping
- If user confirms, update version in all workspace crates
- Amend the commit with version bump
-
Push
- Push to current branch with
git push
- If branch has no upstream, use
git push -u origin <branch>
-
Summary
- Report what was shipped:
- Commit hash
- Branch name
- Files changed
- Version (if bumped)
Usage
/ship
/ship bump
/ship --dry-run
Safeguards
- Always run full build + test suite before committing
- Never force push
- Never skip hooks (no --no-verify)
- Show clear summary of what will be committed before proceeding
- Fail fast on any build/test error
Expected Outcome
All changes committed, tested, and pushed to remote with proper conventional commit message.