agentleFS
Sign inStart free
blauwtjeblauwtje/exo/skills/ship/SKILL.md

ship

Skill1 starsChanged 53 days agoMITView on GitHub

Use when commits may leave the machine, or the user asks to push, open, watch or merge a pull request or fix its failing checks, conflicts or review comments. Not for reviewing code, an unnamed PR, or a release.

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, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 180 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Read references/pr-merge.md for routes the menu skips.

    line 21
  2. Very specific:

    No issue: node "${CLAUDE_PLUGIN_ROOT}/skills/ship/scripts/repo-fields.mjs" and its --size form.

    line 25
  3. Very specific:

    After a fix, rerun 5; no --merge.

    line 30

“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

Goal: ship only as the user says.

  1. Authorize. Letter, non-ask ship setting or merge request authorizes the route.
    • Watching or comments authorize only fix commits, push and replies, not force, --no-verify or a relaxed gate/test.
  2. Overview: ../../lib/references/closing.md, three lines, then the question.
    • Changed, Verified go only to run report.
    • From gate, its lines replace overview.
    • A named follow-up adds Follow-up: <what>, no issue filed; say so to file one. No gh issue create before the yes.
  3. Ask. Quote the stdout of node "${CLAUDE_SKILL_DIR}/scripts/ship.mjs" --routes as the menu; nothing leaves the machine before the letter.
    • Read references/pr-merge.md for routes the menu skips.
    • A set route: skips asking; explain an unapplied ship=.
    • --land → take the menu's (A) with no question.
  4. PR body for open-pr/pr-merge with Closes #<n>.
    • No issue: node "${CLAUDE_PLUGIN_ROOT}/skills/ship/scripts/repo-fields.mjs" and its --size form.
  5. Verify, for pr-merge: hand diff to gate; FAIL pushes nothing.
    • Record or reuse verdict: references/pr-merge.md.
  6. Route. node "${CLAUDE_SKILL_DIR}/scripts/ship.mjs" --route <push|open-pr|pr-merge> --title <subject> --body <file> [--issue <n>] [--method squash|merge|rebase] under run_in_background.
    • Push, open, wait for checks (stops after 20 minutes, exit 124; read output at least every 10 min), gate from API, merge, confirm.
    • After a fix, rerun 5; no --merge.
  7. Merge. List and verify each: references/pr-merge.md.
    • node "${CLAUDE_SKILL_DIR}/scripts/ship.mjs" --merge <n...> under run_in_background gates and merges each. A stop halts no other.
  8. Comments and watching per their references.

References

FileRead it when
references/fields.md4 fields.
../../lib/references/question.md3, DIRTY.
references/pr-prep.md4 body.
references/commit-split.mdDirty tree.
references/stack.mdStacked PRs.
references/fix-ci.mdFailing check, watch.
references/merge-conflicts.mdConflicts, 6, watch.
references/pr-comments.mdComments, watch.
references/watch.mdWatching.
references/pr-merge.md3, 5, 7.
../../lib/references/closing.mdBefore the report.

Report: each line ship.mjs prints, checkout line (branch for Keep local), status gh pr view <n> --json state,isDraft, gh pr ready <n> if draft, if merged node "${CLAUDE_SKILL_DIR}/../build/scripts/remove-worktree.mjs" --kept --worktree <path> --run ., refused → leave it, report it.

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