chrishobbsrocks

Sprint Ship — Development skill for Claude Code

Development community

Pipeman: push code to remote after dev work is agreed done.

How to install Sprint Ship

Installs to ~/.claude/commands/chrishobbsrocks-fully-completely-sprint-ship.md

Terminal
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/chrishobbsrocks/fully-completely/HEAD/.claude/commands/sprint-ship.md -o ~/.claude/commands/chrishobbsrocks-fully-completely-sprint-ship.md

Restart Claude Code, or start a new session, for it to be picked up.

What Sprint Ship does


description: "Pipeman: push code to remote after dev work is agreed done" allowed-tools: [Bash]

Ship Sprint

Usage: `/sprint-ship --commit `

python3 scripts/sprint_lifecycle.py ship $ARGUMENTS

Only succeeds once Dev Team has run `/sprint-dev-done`. Moves the sprint into the `liveqa_live` phase, LiveQA should now test the deployed product with `/sprint-liveqa`.

Alternatives in Development

  • Dev — Switch to Dev Work mode - optimized for software development 2.8k ★
  • Overnight PRs — Autonomous overnight loop — verify issues against the codebase, close stale ones, ship PRs through /ship (bug 324 ★
  • Obsidian Log — Log this work or dev session to the vault — infers project from context 277 ★

Full documentation available on GitHub

View Source Repository