agentleFS
eugnmueller-87eugnmueller-87/claude-blueprint/.claude/skills/ship/SKILL.md

ship

Skill1 starsChanged 5 months agoMITView on GitHub

Land the current change end to end — branch if needed, run lint/typecheck/tests, self-review the diff, make a conventional commit, push, and open a PR. Refuses to push to main/master. Reports honestly if any gate fails and stops. Trigger phrases "ship it", "ship this", "land this change".

  • Commits and pushes

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 9 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

  • 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

  • ShreyRaviSkill

    setup-gbrain

    Set up gbrain for this coding agent: install the CLI, initialize a local PGLite or Supabase brain, register MCP, capture per-remote trust policy. One command from zero to "gbrain is running, and this agent can call it." Use when: "setup gbrain", "connect gbrain", "start gbrain", "install gbrain", "configure gbrain for this machine". (gstack)

    Also in 7 projects that use this

  • +1 more from ShreyRavi

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. Distinctive:

    If any gate fails: print the failing output, name the fix, STOP.

    line 32
  2. Very specific:

    Self-review: Run the pr-review skill on the staged diff.

    line 34
  3. Distinctive:

    Don't ship over a known real bug.

    line 36
  4. Distinctive:

    If you stopped early, report exactly which gate and why — honestly.

    line 58

“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

Trigger: "ship it" / "ship this" / "land this change"

Standing rules: ../_conventions.md.

Land the change cleanly. Every gate must actually pass — never report "shipped" if a step failed. If a gate fails, STOP at that gate, show the real failure, and give the one fix to try. No hedging, no "should be fine".

Steps

  1. Branch guard. git branch --show-current. If on main/master, create a feature branch first: git switch -c <type>/<short-desc> (type = feat / fix / chore / refactor). The block-dangerous-commands hook also refuses a push to main — this is the friendly first line.
  2. Scope check. git diff --stat. If the diff spans unrelated concerns, say so and offer to split — don't silently ship a mixed bag.
  3. Quality gates (run, capture output, STOP on first failure):
    • Format: ruff format . (Python) or the detected formatter.
    • Lint: ruff check . (Python) / npm run lint (JS).
    • Types: mypy . (if configured) / npm run typecheck. Skip cleanly if the project has no type checker — say you skipped it.
    • Tests: pytest (Python) / npm test. Run the FULL suite before a ship. If any gate fails: print the failing output, name the fix, STOP. Do not commit.
  4. Self-review. Run the pr-review skill on the staged diff. Fix any correctness finding at ≥80% confidence before committing. Don't ship over a known real bug.
  5. Secret sweep. Re-check the staged diff for secrets (the scan-secrets hook guards writes, but confirm here): keys must come from env vars, never literals. If anything looks like a real key, STOP.
  6. Commit. Conventional commit, imperative subject, WHY in the body. End the message with:

    Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
  7. Push + PR. git push -u origin <branch> then gh pr create with a body that states what changed and why, plus the test evidence from step 3. End the PR body with:

    🤖 Generated with [Claude Code](https://claude.com/claude-code)
  8. Report (terse): branch · gates passed (with actual pass counts) · PR url. If you stopped early, report exactly which gate and why — honestly.

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.