agentleFS
Sign inStart free
eigent-aieigent-ai/agent-skills/skills/coding-agents-and-ides/ship/SKILL.md

ship

Skill27 starsChanged 8 months agoApache-2.0View on GitHub

Plan launch readiness, staged rollouts, production monitoring, rollback, communications, and post-launch validation. Use when the user asks for `/ship`, pre-launch checklists, release readiness, staged rollout plans, feature flags, deployment monitoring, or rollback planning.

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ios-sync, open-gstack-browser and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Saqlain-811Skill

    ios-sync

    Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)

    Also in 6 projects that use this

  • seek888Skill

    open-gstack-browser

    Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

    Also in 10 projects that use this

  • ayudaySkill

    setup-deploy

    Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".

    Also in 19 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 9 projects that use this

  • zebbernSkill

    debug-fix

    Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)

    Also in 4 projects that use this

  • ramybarsoumSkill

    document-release

    Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped.

    Also in 23 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 180 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to prepare a feature or change for production.

    line 10
  2. Distinctive:

    Create rollback and mitigation steps:

    line 21
  3. Distinctive:

    After launch, compare live metrics against expected ranges and decide whether to continue, pause, expand, or roll back.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 180 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ship

Overview

Use this skill to prepare a feature or change for production. The goal is to make launch decisions explicit: what ships, how it rolls out, what is monitored, when to stop, and how to recover.

Workflow

  1. Identify the release scope, owner, timeline, users affected, dependencies, and risk level.
  2. Build a pre-launch checklist:
    • Tests, migrations, feature flags, documentation, support readiness, analytics, alerts, and runbooks.
  3. Define rollout strategy:
    • Internal, beta, percentage rollout, region/account cohorts, or all-at-once when low risk.
  4. Specify success metrics and guardrails:
    • Product metrics, reliability metrics, error rates, latency, revenue, support volume, and user feedback.
  5. Create rollback and mitigation steps:
    • Flag disablement, revert path, data repair, comms, and owner escalation.
  6. Plan launch communications for affected teams and users.
  7. After launch, compare live metrics against expected ranges and decide whether to continue, pause, expand, or roll back.

Output Pattern

  • Release summary.
  • Pre-launch checklist.
  • Rollout stages and entry/exit criteria.
  • Monitoring plan.
  • Rollback plan.
  • Communications plan.
  • Post-launch validation steps.

Example Prompts

  • /ship - We're deploying the new payments flow tomorrow. Walk me through the pre-launch checklist, what to monitor in the first hour, and our rollback plan if error rates spike.
  • /ship - Plan a staged rollout for our new recommendation engine. Start at 5% traffic, define success metrics, and set the criteria for each expansion step to 100%.
  • /ship - We shipped 3 hours ago. Here are the current metrics [paste]. Is anything outside normal range? Should we roll back or keep going?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free