agentmods.dev

ship

A command that prepares a structured release checklist after code review and commit, covering deployment checks, rollback, monitoring, feature flags, rollout, and release notes.

In plain words
What is it for?
Use it before deployment to create a ship plan and deployment command for the user to run; it does not deploy the application itself.
Why use it?
It gathers the feature's specification, design, tasks, validation result, and review decision so deployment preparation is based on the recorded project details.

Command for Claude Code

57 2mo ago A scan 18 tokens original MIT
View the source file loiane/specs-driven-development-spring-angular
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/loiane/specs-driven-development-spring-angular/ship
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,027 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.01027
Opus 5 $0.00009 $0.00513
Sonnet 5 $0.00004 $0.00205
Haiku 4.5 $0.00002 $0.00103

Measured yesterday against content hash 6952be998146, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ship scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/ship.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/ship

Phase: 8 — ship (post-commit, pre-deploy hygiene) Owning agent: .claude/agents/spring-code-reviewer.md (reused; no new persona) Skills used: shipping-and-launch, spring-security-baseline, flyway-or-liquibase-detection

Purpose

After /review approves the diff and the user commits, produce a structured ship plan that verifies pre-deploy gates, captures rollback + observability + flag posture, plans the staged rollout, and drafts release notes. The agent never deploys — it prints the deploy command for the user to run.

Inputs

  • <feature-id> (optional). Defaults to the most recent feature with an 08-code-review.md verdict of Approve or Approve with waivers.
  • Optional --base <ref> (defaults to origin/main) for diff and release-note generation.

Reads

  • .specs/<feature-id>/01-spec.md — ## Goal, AC list, any open Q-NNN.
  • .specs/<feature-id>/03-design.md — migration plan, security posture, any open Q-NNN.
  • .specs/<feature-id>/04-tasks.md — files_in_scope for diff-scope check.
  • .specs/<feature-id>/07-validation-report.md — verdict must be PASS.
  • .specs/<feature-id>/08-code-review.md — verdict must be Approve or Approve with waivers.
  • .specs/_baseline.json — for regression check.
  • git diff <base>...HEAD and git log <base>..HEAD — for migration classification, new-endpoint detection, release-note drafting.
  • .claude/skills/shipping-and-launch/SKILL.md (authoritative behavior).
  • .claude/templates/ship-plan.template.md.

Writes

  • .specs/<feature-id>/09-ship-plan.md.

Process

  1. Resolve feature. If no <feature-id>, pick the most recent feature with 08-code-review.md verdict Approve*. Refuse if none.
  2. Verify pre-ship gates (per shipping-and-launch skill): validation PASS, review Approve*, zero unresolved Q-NNN, no baseline regression, every changed file is in some task's files_in_scope. Halt at the first FAIL with the specific recovery command.
  3. Classify migrations. Walk src/main/resources/db/migration/** (Flyway) or the changelog (Liquibase) hunks in the diff. Tag each script: forward-only safe / expand / contract / breaking. Halt on breaking without an ADR.
  4. Inventory new surface. New REST endpoints, message handlers, scheduled tasks, external HTTP clients. For each, verify a MeterRegistry registration exists in the diff. Halt on missing metric.
  5. Render the ship plan. Fill .claude/templates/ship-plan.template.md — every section non-empty (n/a allowed only with a one-line reason).
  6. Surface human-required inputs as Q-NNN. Flag owner, alert thresholds, rollout cohorts. Halt until the user answers; do not invent.
  7. Draft release notes. Two sections: external (plain English, ≤ 3 bullets, edited by the user before publishing) and internal (diff summary, AC list, ADR links, migration class, flag name, dashboard).
  8. Print deploy command. Suggest the team's release-pipeline trigger or kubectl rollout / mvn deploy line. The agent never executes it.

Read the full file on GitHub · 54 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 54 lines · 18 tokens per session scan A 6952be998146

Subscribe to this mod's changes

ship is a command published in the GitHub repository loiane/specs-driven-development-spring-angular (57 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,027 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code reviewGit and workflowTestingangulargithub-copilotjavaspec-driven-developmentspring-boottdd
Related

Other commands, from other repositories

devkit.refactor

Provides guided code refactoring capability with deep codebase understanding, compatibility options, and comprehensive verification. Use when restructuring or improving existing code.

giuseppe-trisciuoglio/developer-kit · 27 tokens

spec-kitty.analyze

Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.

Priivacy-ai/spec-kitty · 0 tokens

devkit.verify-skill

Validates a skill against DevKit standards (requirements, template, dependencies). Use when you need to verify a skill before publishing or after modifications.

giuseppe-trisciuoglio/developer-kit · 29 tokens

devkit.prompt-optimize

Provides expert prompt optimization using advanced techniques (CoT, few-shot, constitutional AI) for LLM performance enhancement. Use when you need to improve prompt quality or optimize LLM interactions.

giuseppe-trisciuoglio/developer-kit · 37 tokens

sdd-plan

Turn a spec into a persisted baby-step plan file — research, resume, impact analysis.

GregorBiswanger/featherspec · 18 tokens

sdd-architecture-update

Detect architecture drift and sync the snapshot + Memory Bank (with confirmation).

GregorBiswanger/featherspec · 14 tokens