damilola-elegbede-org /ship-it
Usage
/ship-it # Full: docs → test → review → commit-push-pr
/ship-it -c -p # Quick: delegate commit+push to commit-commands:commit-push-pr (no PR)
/ship-it -t -c -p # Test first, then commit+push
/ship-it -r -c -p # Review gate, then commit+push
/ship-it -d -t -c -r -p # Everything except PR
/ship-it -pr # Just create PR (uses /pr for CodeRabbit acknowledgment if present)
/ship-it --dry-run # Preview without executing
Description
A thin orchestrator that runs heavy optional steps (docs, test, review) and
then delegates the commit/push/pr triplet to the Anthropic-published
commit-commands:commit-push-pr skill — a 21-line skill that does all three
git operations in a single tool message. That's the lean common path.
When a step needs features specific to our skills (e.g., the CodeRabbit
PR-comment integration in /pr, or --dry-run in /push), /ship-it falls
back to invoking our own skill instead.
Flags
| Flag | What it enables |
|---|---|
-d |
Run /docs first |
-t |
Run /test first |
-v |
Run /verify first (gates must be green to proceed) |
-r |
Run /review first |
-c -p -pr |
Commit + push + PR (delegated to commit-commands:commit-push-pr) |
-c -p (no -pr) |
Commit + push only (commit-commands:commit-push-pr without the PR step is not available, so fall back to /commit + /push) |
-c alone |
Run /commit only |
-p alone |
Run /push only |
-pr alone |
Create PR via /pr (preserves --draft, CodeRabbit acknowledgment) |
| Other combinations | Any other partial combination (e.g., -c -pr without -p) is rejected with an error. |
--dry-run |
Print the plan, don't execute |
Execution
Parse flags from $ARGUMENTS. With no flags, enable every step.
Run enabled steps in this fixed order; halt immediately on failure.
Pre-commit gate. Before any step that commits, pushes, or opens a PR, the project's gates
must have been run in this invocation. Only -v satisfies that: /test runs the test suite but
not lint, typecheck, or build, and /review reads code and runs no gates at all. A green -t
with a red typecheck is exactly the state this gate exists to catch.
IF: any of -c / -p / -pr is set AND -v did not run and pass
RUN: /verify --report-only
IF: any gate failed
OUTPUT: "Refusing to ship with N failing gate(s): {names}. Fix them and re-run."
HALT
IF: no gates detected
OUTPUT: "No verification gates detected — shipping unchecked."
CONTINUE (this is a warning, not a failure; a project with no gates is allowed to exist)
What this gate is, honestly. It is a convention this skill follows, not a control that
enforces itself. Nothing stops an agent from calling /commit directly and skipping it entirely —
bare /commit carries no gate of its own. Treat it as the default path being the safe one, not as
a guarantee. Making it a guarantee needs a PreToolUse hook on git commit that checks for a
fresh verify result; that is a larger change than this skill.
There is deliberately no bypass flag. /commit and /push already carry a standing rule against
skipping hooks, and a settings hook blocks that string in any bash command outright, so a skip
flag here would reopen the hole those guards close — and documenting it would put the blocked
string into the example output. To ship a red branch, fix the gate or run /push directly and own
that choice.
-d: Invoke/docs. Skip if no doc-relevant changes detected.-t: Invoke/test.-v: Invoke/verify. Halt if it ends with gates still failing.-r: Invoke/review. If issues found, hand off to/resolve-commentsper its own flow.- Commit + push + PR (after any of -d/-t/-v/-r have run): pick the right path
based on which of
-c,-p,-prare set (in the no-flag default, all three are set, so this step runscommit-commands:commit-push-pr):- All three of
-c -p -prset (including the no-flag default):- Check that
commit-commands:commit-push-pris available (the Anthropic-publishedcommit-commandsplugin installs it). - If available: one tool call to
commit-commands:commit-push-pr. No TaskCreate ceremony, no orchestration. - If not available: output
commit-commands:commit-push-pr not installed, falling back to local skillsand invoke our/commit→/push→/prin sequence.
- Check that
-c -pwithout-pr:commit-commands:commit-push-pralways creates a PR, so for "commit + push only" invoke our/commitfollowed by/push.-pralone or alongside only-d/-t/-r(not-c/-p): invoke our/prso the CodeRabbit comment integration (via.tmp/coderabbit-ignored.json) and flags like--draftwork.-calone: invoke our/commit.-palone: invoke our/push.- Other partial combinations (e.g.,
-c -prwithout-p): reject with a clear error before doing any work.
- All three of
Why delegate to commit-commands:commit-push-pr for the common case: it does
status + commit + push + gh pr create in a single message with parallel tool
calls (its frontmatter pre-injects git status, git diff HEAD, and the
current branch — no extra round-trips). For routine ship-it invocations, that
beats our previous chain of TaskCreate ceremony + 3 sequential sub-skills.
Dry-run
When --dry-run is set, print the enabled steps and which path will run for
the commit/push/pr triplet. Don't execute anything.
Expected Output
🚀 ship-it: docs → test → review → commit-push-pr
📋 /docs
✅ done
📋 /test
✅ done
📋 /review
✅ done
📋 commit-commands:commit-push-pr
✅ commit + push + PR
PR: https://github.com/org/repo/pull/123
Notes
- Halts immediately on any step failure.
commit-commands:commit-push-pris published by Anthropic in thecommit-commandsplugin. If it isn't installed, fall back to our/commit+/push+/prchain./prretains its CodeRabbit-acknowledgment behavior —/ship-it -pr(or any path that uses our/pr) will post the.tmp/coderabbit-ignored.jsonsummary to the PR.- Each invoked command handles its own validation (main/master checks, existing PR, etc.).