agentleFS
joelhooksjoelhooks/uncomplect/skills/ship/SKILL.md

ship

Skill2 starsChanged 36 days agoMITView on GitHub

Learn how to ship a change through merge, CI, release, stage deployment, rollout, verification, rollback and flags.

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

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 14

    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:

    Read AGENTS.md first. Use the project mapping for commands, approval boundaries, owners and evidence.

    line 20
  2. Distinctive:

    Follow the project's rules for who may merge, branch protection, and the order of dependent pull requests.

    line 63
  3. Distinctive:

    WAIT[candidate-ci]: stop until the merged commit passes CI and has the required stage checks.

    line 69
  4. Distinctive:

    Read CI and stage qualification and flags.

    line 71
  5. Distinctive:

    Read runner selection and deploy keys.

    line 75
  6. Distinctive:

    Use only deployment features marked on.

    line 77
  7. Distinctive:

    No release queue or scheduler is implemented here.

    line 83
  8. Distinctive:

    Check each release's exact version.

    line 85
  9. Distinctive:

    Read gradual rollout, canary and [post-deploy

    line 89
  10. Distinctive:

    Read rollback before restoration.

    line 95
  11. Distinctive:

    Follow the project's destroy refusal.

    line 107
  12. Distinctive:

    Keep this skill aligned with the available deployment features in the same change.

    line 111
  13. Distinctive:

    Read catalog maintenance before changing deployment availability.

    line 113
  14. Distinctive:

    Keep this procedure and its references generic.

    line 115

“Common” is measured: kept by at least 6 in 10 of the 181 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 a change

Read AGENTS.md first. Use the project mapping for commands, approval boundaries, owners and evidence.

Terms used here

  • Candidate: the exact commit and deployment version being considered for release.
  • Stage: a named deployment environment, such as production.
  • Canary: an isolated deployment used to check a candidate before wider release. The project mapping determines its allowed test traffic.
  • Promotion: making a checked candidate active.
  • Qualification: passing the named checks required for that exact version or behavior.
  • Readback: reading deployed state from the provider to confirm the active version.
  • Adapter: the implementation that connects the release procedure to a deployment provider.
  • Rollback: making a recorded earlier version active without rebuilding it. It does not undo stored data or database changes.
  • Flag: an approved switch that controls whether a behavior is enabled.
  • CI: continuous integration, the automated checks run for a commit.
  • CLI: command-line interface, a program called through terminal commands.
  • Effect: the library for describing work with typed failures and required services.
  • Service: a named interface for one job.
  • WAIT: a procedure stop until its named condition has evidence. It is not a running scheduler.
  • HOLD: a stopped release awaiting a decision. It does not declare a failed check or trigger rollback.

1. Read current deployment availability

<!-- deploy-confidence:start -->

Continuous deployment is off.

  • Automatic production deploy: off.
  • Automatic stage deploy: off.
  • Automatic rollback after promotion: off.
  • Automatic rollback before promotion: off.
  • Provisioned canary stage: off.
  • Gradual rollout: off.
  • Deploy runner: local (checked with local test fixtures only; not proven in production).

Off means unavailable for operational use, even if code or fixture tests exist.

<!-- deploy-confidence:end -->

2. Prepare and merge

Ship one small release per pull request (PR). Keep new behavior behind its approved flag until its required checks pass.

Record the exact candidate commit and deployment version, base version, observed code and infrastructure changes, and release owner. Record the version to restore if the release fails. Use fast commit checks locally. CI runs the full suite against that candidate.

Follow the project's rules for who may merge, branch protection, and the order of dependent pull requests. Do not bypass hooks or put approval policy in merge tooling.

Merging

When the project uses label-free Kodiak, a ready PR merges itself once required CI passes. Kodiak is the service that merges eligible pull requests. Open a PR only when it is meant to merge; add NO MERGE to hold it. Kodiak skips drafts and squash-merges eligible PRs. The lane fixes merge conflicts. Read the project mapping for the order of dependent pull requests and blocking labels.

WAIT[candidate-ci]: stop until the merged commit passes CI and has the required stage checks. A PR proof does not cover a different merged commit.

Read CI and stage qualification and flags.

3. Release and deploy

Read runner selection and deploy keys. Code, configuration and authorization are separate facts.

Use only deployment features marked on. When automation is off, the authorized owner follows the project's manual path.

Prepare and verify releases concurrently. Changes to the same deployment stage must run one at a time. WAIT[stage-queue]: stop until the authorized release has its turn for that stage. The latest eligible candidate replaces older queued candidates; record that outcome.

Name the exact commit you ship, and respect the stage's quiet windows. Put these guards in the deploy driver, never in a shell wrapper around it.

No release queue or scheduler is implemented here. The authorized owner must enforce the sequence through the project's manual procedure.

Check each release's exact version. Do not wait for another release's post-deploy check. Require an observed plan and read the deployed version back from the provider. Stored data must remain readable by both the candidate and the version that may be restored.

4. Roll out and verify

Read gradual rollout, canary and post-deploy checks.

Report code-ready, deployed and behavior-verified separately. Check customer-facing outcomes signed out, as the recipient would.

5. Restore or stop

Read rollback before restoration.

StopCondition needed to continue
WAIT[release-scope]Authorization and the target stage are known.
WAIT[adapter-qualification]The required behavior checks have passed for the adapter.
WAIT[rollback-target]The version to restore is recorded and usable.

Missing evidence stops deployment. An observed failed check follows the project's failure policy. HOLD waits for a decision; it does not trigger rollback.

The release machine tracks deployment states and transitions. Follow its policy for observed failures. Do not expand the approved scope to credentials, infrastructure, data formats, provider writes, or messages to real recipients.

Follow the project's destroy refusal. Rollback makes the previous known-good version active immediately, without rebuilding it or waiting for a fixed observation period. Read the active version back from the provider to verify it. It restores code only.

6. Keep one release procedure current

Keep this skill aligned with the available deployment features in the same change. The current implementation has no generated list of recorded releases or generated deployment-availability block.

Read catalog maintenance before changing deployment availability.

Keep this procedure and its references generic. Keep project facts behind the project mapping. Keep executable logic in the owning Effect packages and CLIs.

Skill scripts are thin launchers only. Use the project's maintenance skill to keep dependencies and enforced checks current.

The current implementation has no shared record of blocked release steps. WAIT labels above name manual procedure stops. The scheduler remains unimplemented. Missing evidence stops deployment.

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.