agentleFS
SwitchbackTechSwitchbackTech/compass/.agents/skills/ship/SKILL.md

ship

Skill227 starsChanged 50 days agoMITView on GitHub

Take the current branch from working tree to a ready PR that the merge queue merges. Use when the user says "ship" or a loop prompt reaches the PR step.

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

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

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Self-check: Read the complete base-to-head diff as a stranger would: state, races, cleanup, keyboard and focus paths, accessibility, auth, …

    line 32
  2. Distinctive:

    No label is involved. The required checks are the whole gate: no line-count rail, no path denylist, nothing to look for or wait on.

    line 45
  3. Distinctive:

    Do not wait for a human on a PR that is green and mergeable.

    line 48
  4. Distinctive:

    Never close/reopen the PR, push empty commits, or merge main in just to re-run CI (merge main only for a real conflict).

    line 54

“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

Status lives on the GitHub issue (labels, open PR, closed state). Nothing in the repo records it.

Steps

  1. Preflight. git status; work on a branch off origin/main, never on main; gh auth status; find any existing PR for the branch.
  2. Verify. bun run verify --strict. Fix failures and rerun, at most two retries. VERDICT: INCOMPLETE means Chromium is missing: run bunx playwright install chromium and rerun. Never weaken a test, widen a timeout, or change test order to get there.

    The local verdict is evidence; CI is the gate. When test:web, test:a11y, or test:e2e fails, verify reruns the failing files on the branch and on origin/main in a temporary worktree and prints a Baseline against origin/main: block that sorts each failure into NEW (fails only on the branch), PRE-EXISTING (fails on main too), or FLAKY (passed on rerun). Only NEW failures make the verdict FAIL; fix those. Paste the PRE-EXISTING and FLAKY lists into the PR body as-is. A failure verify cannot classify (a crash, an error outside a test) stays FAIL; show why it is environmental in the PR or treat it as real.

  3. Self-check. Read the complete base-to-head diff as a stranger would: state, races, cleanup, keyboard and focus paths, accessibility, auth, data loss. If the diff added more than a screen of new abstraction, run the simplify skill. Confirmed problems become isolated fix commits, then rerun step 2.
  4. PR. Open a draft PR against main using .github/PULL_REQUEST_TEMPLATE.md: Fixes #N, what changed and why, the pasted VERDICT: line and checks run. No unchecked manual-testing boxes. Mark it ready once step 2 is satisfied; reviews run on ready PRs only, so a draft that never becomes ready is a stop, not a handoff.
  5. Merge. Mark the PR ready and run gh pr merge --auto. main takes changes only through the merge queue, so a direct merge is refused by rule; GitHub squash-merges through the queue once required checks pass. No label is involved. The required checks are the whole gate: no line-count rail, no path denylist, nothing to look for or wait on.

    Do not wait for a human on a PR that is green and mergeable. If the queue drops the PR on a check the diff cannot reach (a runner timeout, a UI test in a surface you did not touch) and the same check passed on the PR head, say so once on the PR and run gh pr merge --auto again. A second drop for the same reason is a human call: comment the evidence and stop.

    Never close/reopen the PR, push empty commits, or merge main in just to re-run CI (merge main only for a real conflict).

Escalate

Comment on the issue with the decision needed, the recommended option, and the cost of waiting, then label agent-loop-needs-human. Reasons: product ambiguity, production deploy, secrets, OAuth grants, deletion, access grants, verify still failing after two retries.

Anti-patterns

See anti-patterns.md.

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.