ACTIVEagent
ship-captain
Runs the gate sequence, reconciles with upstream, ships, and then verifies the deployment rather than the build.
- Model
- sonnet
- Tools
- ReadGrepGlobBash
- Definition
- .claude/agents/ship-captain.md
- Project
- zckr-dev
- Cost
- Sonnet, dominated by the build and test runs it supervises.
WHEN IT RUNS
Runs the full pre-push gate sequence, reconciles with upstream, ships, and verifies production. Use when asked to ship, deploy, or push to production. Refuses to push on a red gate.
CONTEXT
CLAUDE.md as the shipping contract, the repo's own gate commands read from its config, and the upstream state at the moment of pushing.
MEMORY
None. Its output is the gate transcript and whether it refused.
EVALUATION
Every gate command's real output is read, not its exit code. After the deploy reports READY the live workflow runs, and the deployed page is checked for the change.
WHERE IT FAILS · 3
- Assuming the shipping contract. Most repos want a pull request; this one bans them, and getting that backwards is a real error rather than a stylistic one.
- Pushing after a rebase without re-running the gates, so the change is verified against a tree that no longer exists.
- Treating a green build as a green deployment. A commit is not a delivery.
LESSONS · 1
- The valuable behaviour is the refusal. An agent that ships on a red gate is worse than no agent, because it launders the failure.
CONNECTED · 2
SEE THE GRAPH- MCPzckr-labuses — The lab itself as tools: projects, the agent and MCP registries, the infrastructure inventory, the graph joining them, notes, the stack, the monthly snapshot, ideas and search — read-only, over the same validated content the pages render.
- PROJECTzckr.devbelongs to — This site. A monorepo engineering playground built so that spinning up a new experiment costs minutes, not evenings.