agentleFS
Sign inStart free
therapystherapys/dotagents/skills/ship/SKILL.md

ship

Skill8 starsChanged 2 months agoMITView on GitHub

Take the current changes from a dirty tree to an open pull request — branch, commit, push, and open the PR. Use when the user says any of: 'create a pr to main/dev', 'open a pr', 'push to main', 'commit and push', 'push this to git', 'ship it', 'push to the linear branch and open a draft PR', or asks to do the same across multiple repos ('push to each repo except infra').

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 182 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Base branch is main: Only target dev when the user explicitly says "to dev".

    line 12
  2. Very specific:

    Never target or push directly onto main/dev for feature work — always go through a branch + PR, even when the user says "push to main" …

    line 17
  3. Very specific:

    Branch: if currently on main/dev, create the correctly-named branch (see conventions) and switch to it.

    line 22
  4. Very specific:

    Commit: follow the commit skill for the message (Conventional Commits subject).

    line 23
  5. Distinctive:

    Run steps 1–5 per repo that has changes.

    line 34
  6. Very specific:

    If there are unrelated/ambiguous staged files, ask which to include before committing (per the commit skill).

    line 39
  7. Distinctive:

    Don't force-push. Don't amend or rebase shared history unless asked.

    line 40
  8. Distinctive:

    If a Linear issue id was given, after opening the PR, offer to move the issue to "In Review" / link the PR via the Linear MCP — do it only …

    line 41

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

One flow from working changes to an open PR. Delegates the commit message to the commit skill; owns everything around it (branch, push, PR).

Conventions

  • Base branch is main. Only target dev when the user explicitly says "to dev".
  • Branch naming:
    • Linear issue given (e.g. ABC-123): name the branch <id>/<slug> (lowercase id + short kebab slug from the issue title), matching Linear's copy-branch format. Use the Linear MCP to fetch the issue title for the slug when available.
    • Otherwise: feat/<slug> for features, fix/<slug> for bug fixes (mirrors existing branches).
  • PR is a normal PR by default. Open a draft only when the user says "draft".
  • Never target or push directly onto main/dev for feature work — always go through a branch + PR, even when the user says "push to main" (that means "get it onto main via a PR").

Steps

  1. git status / git diff to understand the changes and the current branch.
  2. Branch: if currently on main/dev, create the correctly-named branch (see conventions) and switch to it. If already on a suitable feature branch, stay.
  3. Commit: follow the commit skill for the message (Conventional Commits subject). Honor any file scoping or guidance in the user's prompt.
  4. Push: git push -u origin <branch>.
  5. Open PR: gh pr create --base <main|dev> --title "<subject>" --body "<short summary>" (add --draft only if requested). Prefer --fill when the commit subject/body already say enough.
  6. Return the PR URL. If CI matters, hand off to fix-ci.

Multi-repo mode

Trigger: "on each of the repos", "all repos except infra", "push to git on each repo".

  • Target set = the sibling git repos under a shared parent dir.
  • Honor any excludes the user names (e.g. "except infra").
  • Run steps 1–5 per repo that has changes. Skip clean repos and report them as skipped.
  • Summarize at the end: one line per repo → branch + PR URL (or "no changes").

Guardrails

  • If there are unrelated/ambiguous staged files, ask which to include before committing (per the commit skill).
  • Don't force-push. Don't amend or rebase shared history unless asked.
  • If a Linear issue id was given, after opening the PR, offer to move the issue to "In Review" / link the PR via the Linear MCP — do it only if the user confirms.

Download now (ZIP)

  • Other versions194 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 194

    1. garrytan/gstack★ 139ksame name
    2. rtk-ai/rtk★ 85ksame name
    3. simstudioai/sim★ 30ksame name
    4. millionco/react-doctor★ 15ksame name
    5. BuilderIO/agent-native★ 7.4ksame name
    6. fallow-rs/fallow★ 5.1ksame name
    7. nightly-labs/openbot★ 4.4ksame name
    8. plugin87/ux-ui-agent-skills★ 3.1ksame name
    9. ShenSeanChen/waku-agent★ 2ksame name
    10. DenchHQ/DenchClaw★ 1.7ksame name

    184 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects 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 18 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

    • 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 8 projects that use this

    • ayudaySkill

      unfreeze

      Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits".

      Also in 21 projects that use this

  • In this repository20 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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