agentleFS
Sign inStart free
whyashthakkerwhyashthakker/estack/skills/ship/SKILL.md

ship

Skill0 starsChanged 11 days agoMITView on GitHub

Finish and ship a change safely. Checks what changed, runs the project's own typecheck, lint, and tests, stages only the files this task touched, writes a short commit message, updates the changelog only for real product changes, and pushes after the user agrees. Use when the user says "ship it", "push", "commit and push", "deploy", "we're done", or asks to update release notes.

  • Reads credentials

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

  • 0

    Common

    Most of the 180 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Run git status, git diff --stat, and git log origin/<branch>..HEAD.

    line 12
  2. Very specific:

    Never stage .env*, secrets, large binaries, or build output.

    line 16
  3. Distinctive:

    Follow the repo's own conventions if it has them (look at git log).

    line 32
  4. Distinctive:

    Commit hash, what shipped, what you did not stage and why, and the checks that ran.

    line 40

“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: the change lands clean, small, and easy to undo. Nothing extra goes with it.

1. Look at what changed

Run git status, git diff --stat, and git log origin/<branch>..HEAD. Sort the files into:

  • This task: files you or the user changed for this work.
  • Not this task: other edits in the tree (another agent, another session, the user's work in progress). Do not stage these. List them for the user.

Never stage .env*, secrets, large binaries, or build output.

2. Check

Find the project's own commands (package.json scripts, Makefile, justfile, CI config) and run the fast ones: typecheck, lint, unit tests for the touched area. Ask before a slow full build.

Confirm that each check really ran: read the output, not only the exit code. A command that was not found, or a test runner that found zero tests, is not a pass. If a check fails, fix it or stop and report. Do not ship red.

3. Changelog (only for product changes)

Update the changelog or release notes only when a user of the product would notice the change: a new feature, a pricing or account change, a redesign, a fixed bug they reported. Content (blog posts, docs copy), refactors, and internal tools do not go in a public changelog. When in doubt, leave it out.

4. Commit

  • Stage paths by name: git add path/a path/b. Not git add -A.
  • Message: one short line in the imperative mood, under about 60 characters ("Add retry to payment webhook"). Add a body only if the reason is not obvious.
  • Follow the repo's own conventions if it has them (look at git log).

5. Push

Ask before you push unless the user already said to. Before you push to the default branch, check whether the push starts a deploy or kills a running job (CI config, deploy hooks). If the push is rejected, pull with rebase, run the checks again, then push. Never force-push a shared branch.

6. Report

Commit hash, what shipped, what you did not stage and why, and the checks that ran.

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