Ship — Workflow

Overview

How the ship skill works, step by step.

Source Workflow

Claude skill workflow.

Step-by-step Workflow

ship — Workflow

Auto-generated from SKILL.md. The skill itself is the source of truth; this is a human-readable map of what it does and how it runs.

What it does & when to use

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)

Triggers

ship
deploy
push to main
create a PR
merge and push
get it deployed

How it works

Workflow outline (sections of SKILL.md):

Preamble (run first)
Plan Mode Safe Operations
Skill Invocation During Plan Mode
Skill routing
AskUserQuestion Format
Artifacts Sync (skill start)
Model-Specific Behavioral Patch (claude)
Voice
Context Recovery
Writing Style (skip entirely if EXPLAIN_LEVEL: terse appears in the preamble echo OR the user's current message explicitly requests terse / no-explanations output)
Completeness Principle — Boil the Lake
Confusion Protocol
Continuous Checkpoint Mode
Context Health (soft directive)
Question Tuning (skip entirely if QUESTION_TUNING: false)
Repo Ownership — See Something, Say Something
Search Before Building
Completion Status Protocol
Operational Self-Improvement
Telemetry (run last)
Plan Status Footer
Step 0: Detect platform and base branch
Step 1: Pre-flight
Review Readiness Dashboard
Step 2: Distribution Pipeline Check
Step 3: Merge the base branch (BEFORE tests)
Step 4: Test Framework Bootstrap
Test Framework Bootstrap
Step 5: Run tests (on merged code)
Test Failure Ownership Triage
Step 6: Eval Suites (conditional)
Step 7: Test Coverage Audit
Affected Pages/Routes
Key Interactions to Verify
Edge Cases
Critical Paths
Step 8: Plan Completion Audit
Implementation Items
Test Items
Migration Items
Cross-Repo / External Items
Step 8.1: Plan Verification
Prior Learnings
Step 8.2: Scope Drift Detection
Step 9: Pre-Landing Review
Confidence Calibration
Design Review (conditional, diff-scoped)
Step 9.1: Review Army — Specialist Dispatch
Step 10: Address Greptile review comments (if PR exists)
Step 11: Adversarial review (always-on)
Capture Learnings
Step 12: Version bump (auto-decide)
Step 13: CHANGELOG (auto-generate)
Step 14: TODOS.md (auto-update)
Step 15: Commit (bisectable chunks)
Step 16: Verification Gate
Step 17: Push
Step 18: Documentation sync (via subagent, before PR creation)
Step 19: Create PR/MR
Summary
Test Coverage
Pre-Landing Review
Design Review
Eval Results
Greptile Review
Scope Drift
Plan Completion
Verification Results
TODOS
Documentation
Test plan
Step 20: Persist ship metrics
Important Rules

Components

Single-file skill — all instructions live in SKILL.md.

Invoke

Slash: /ship
Or a natural-language request matching the triggers above.

Source: SKILL.md in this directory.

Execution Logic

The skill executes when its trigger fires (slash command, natural-language match, or direct invocation). It reads its references, applies its rules, and produces the documented outputs.

Edge Cases

See the source skill's references/ and scripts/ folders for edge-case handling.

Failure Handling

A skill failure surfaces as a tool error or a partial output; never a silent skip. Re-run with --verbose (where applicable) for diagnostics.

Integration Notes

Claude — invoked via the Skill tool with skill: "ship".
Codex — referenced from AGENTS.md if mirrored.
Antigravity — referenced from the workspace agent rules if mirrored.
HQ Project — listed on the landing page Skills section + post-login sidebar.
MD Project (md.sgnk.ai) — file rendered from Skills/Ship/workflow.md.
Obsidian — file rendered with frontmatter + tags.

Usage Examples

Invoke via slash command or natural language matching the skill description.

Source: ~/.claude/skills/ship/WORKFLOW.md