How do I install the Specswarm Ship skill?

Run npx skillmds add majiayu000/specswarm-ship in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Specswarm Ship safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Specswarm Ship?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Specswarm Ship free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Specswarm Ship?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Specswarm Ship by majiayu000 — Agent Skill

Name: Specswarm Ship
Rating: 4.5 (4 reviews)
Author: majiayu000

Specswarm Ship

Systematic quality validation, test verification, and safe merging workflow for deployment/release operations. ALWAYS asks for confirmation when user wants to ship, deploy, merge, release, or complete features to production, merge to main branch, or finalize features. This is a DESTRUCTIVE operation (merges and deletes branches).

majiayu000 217de45 2 files · 3.2 KB Updated Sep 9, 2026 567 repo stars

File contents

SpecSwarm Ship Workflow

Provides natural language access to /specswarm:ship command.

When to Invoke

Trigger this skill when the user mentions:

Shipping, deploying, or releasing features
Merging to main/production
Completing or finishing features
"Ship it" (common casual phrase - ALWAYS confirm)

Examples:

"Ship the authentication feature"
"Deploy to production"
"Merge this to main"
"Ship it" ← Ambiguous - might be casual approval
"Release version 2.0"

Instructions

ALWAYS Confirm (Regardless of Confidence):

Detect that user mentioned shipping/deploying/merging
Extract context about what to ship (if provided)
ALWAYS ask for confirmation using AskUserQuestion tool with this format:

Question: "⚠️ SHIP CONFIRMATION - Destructive Operation"

Description: "This will merge your feature branch to main/parent branch and delete the feature branch. This is a DESTRUCTIVE operation that cannot be easily undone."

Options:
- Option 1 (label: "Yes, ship this feature"): "Merge to main branch and delete feature branch (DESTRUCTIVE)"
- Option 2 (label: "No, cancel"): "Cancel - I'm not ready to ship" (or if this was just casual "ship it" approval)
If user selects Option 1, run: /specswarm:ship
If user selects Option 2, process normally without SpecSwarm
Note: The /specswarm:ship command may have its own confirmation as an additional safety layer

What the Ship Command Does

/specswarm:ship runs complete workflow:

Runs quality analysis and validation
Checks quality threshold (default 80%)
Shows merge plan with confirmation prompt
Merges to parent branch
Cleans up feature branch

Important: This is DESTRUCTIVE - it merges and deletes branches. The command itself may have built-in confirmation as a second safety layer.

Semantic Understanding

This skill should trigger not just on exact keywords, but semantic equivalents:

Ship equivalents: ship, deploy, release, merge, publish, finalize, complete, deliver Target terms: production, main, master, parent branch, live, release

Example

User: "Ship it"

Claude: [Shows AskUserQuestion]
1. Run /specswarm:ship - ⚠️ Merge feature to parent branch (DESTRUCTIVE)
2. Process normally - Handle as regular request

User selects Option 2 (it was casual approval, not actual shipping request)

---name: specswarm-shipdescription: Systematic quality validation, test verification, and safe merging workflow for deployment/release operations. ALWAYS asks for confirmation when user wants to ship, deploy, merge, release, or complete features to production, merge to main branch, or finalize features. This is a DESTRUCTIVE operation (merges and deletes branches).--- # SpecSwarm Ship Workflow Provides natural language access to `/specswarm:ship` command. ## When to Invoke Trigger this skill when the user mentions: - Shipping, deploying, or releasing features - Merging to main/production - Completing or finishing features - "Ship it" (common casual phrase - ALWAYS confirm) **Examples:** - "Ship the authentication feature" - "Deploy to production" - "Merge this to main" - "Ship it" ← Ambiguous - might be casual approval - "Release version 2.0" ## Instructions **ALWAYS Confirm (Regardless of Confidence):** 1. **Detect** that user mentioned shipping/deploying/merging 2. **Extract** context about what to ship (if provided) 3. **ALWAYS ask for confirmation** using AskUserQuestion tool with this format: **Question**: "⚠️ SHIP CONFIRMATION - Destructive Operation" **Description**: "This will merge your feature branch to main/parent branch and delete the feature branch. This is a DESTRUCTIVE operation that cannot be easily undone." **Options**: - **Option 1** (label: "Yes, ship this feature"): "Merge to main branch and delete feature branch (DESTRUCTIVE)" - **Option 2** (label: "No, cancel"): "Cancel - I'm not ready to ship" (or if this was just casual "ship it" approval) 4. **If user selects Option 1**, run: `/specswarm:ship` 5. **If user selects Option 2**, process normally without SpecSwarm 6. **Note**: The `/specswarm:ship` command may have its own confirmation as an additional safety layer ## What the Ship Command Does `/specswarm:ship` runs complete workflow: - Runs quality analysis and validation - Checks quality threshold (default 80%) - **Shows merge plan with confirmation prompt** - Merges to parent branch - Cleans up feature branch **Important:** This is DESTRUCTIVE - it merges and deletes branches. The command itself may have built-in confirmation as a second safety layer. ## Semantic Understanding This skill should trigger not just on exact keywords, but semantic equivalents: **Ship equivalents**: ship, deploy, release, merge, publish, finalize, complete, deliver **Target terms**: production, main, master, parent branch, live, release ## Example ``` User: "Ship it" Claude: [Shows AskUserQuestion] 1. Run /specswarm:ship - ⚠️ Merge feature to parent branch (DESTRUCTIVE) 2. Process normally - Handle as regular request User selects Option 2 (it was casual approval, not actual shipping request) ```

Frequently asked questions