agentleFS
WeaverseWeaverse/.agents/skills/ship/SKILL.md

ship

Skill0 starsChanged 6 days agoMITView on GitHub

Prepare the normal release PR and a draft GitHub release for an already-bumped Weaverse version. Use when explicitly asked to ship; never treat invocation as permission to merge, deploy, tag or publish.

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

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 5

    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:

    Read the repository release policy, actual base/default branches, dirty state and workflow triggers.

    line 10
  2. Distinctive:

    Verify that the version, lockfile and visible changelog already landed in the implementation change before final review and CI.

    line 13
  3. Distinctive:

    If authorized to push, use one explicit branch refspec with follow-tags disabled.

    line 19
  4. Distinctive:

    Read an existing draft before editing it.

    line 29
  5. Distinctive:

    Read back the draft status, tag name and notes.

    line 30
  6. Very specific:

    After publishing, fetch the remote tag into a task-owned inspection ref (do not overwrite an existing local tag).

    line 34

“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 an already-prepared version

  1. Read the repository release policy, actual base/default branches, dirty state and workflow triggers. Reuse the implementation PR and its evidence. If a normal production release PR is required, that is still allowed; a separate version-bump branch or PR is not.
  2. Verify that the version, lockfile and visible changelog already landed in the implementation change before final review and CI. Do not choose a new calendar date or bump at release time. Missing metadata goes back into the same implementation change, followed by the required review and gates. If already merged, disclose missing copy and fold it into the next substantive update, not a bookkeeping-only PR.
  3. Freeze the reviewed commit and tree, and check CI/review on that identity with pr-merge-gates. A moving branch name or historical approval is not the release candidate.
  4. If authorized to push, use one explicit branch refspec with follow-tags disabled. Read triggers before pushing; a bare push workflow may deploy every branch. Never add tags as a side effect of preparing the release.
  5. Draft the GitHub release for the repository's tag convention and the already-bumped version, using the full candidate SHA as target rather than a moving branch. Generated notes replace hand-built contributor lists:

    gh release create "$TAG" --repo "$REPO" --target "$REVIEWED_SHA" \
      --title "$TAG" --draft --generate-notes

    Read an existing draft before editing it. If the tag already exists, resolve it first and stop on a mismatch. Read back the draft status, tag name and notes. Report "draft prepared", not "released".

  6. Merge, deploy and publish only if separately within the approved scope. Follow release-verification and prove production before publishing the tag/Release. If merge strategy changes the commit SHA, re-bind review and deployment evidence to the resulting commit; tree equivalence alone is not SHA equality.
  7. After publishing, fetch the remote tag into a task-owned inspection ref (do not overwrite an existing local tag). Peel annotated tags with git rev-parse "$TAG_REF^{commit}" and require equality with the reviewed and deployed commit. target_commitish, a release page and git ls-remote's annotated tag-object ID alone are not proof of the commit. Stop on a mismatch; do not move a published tag to hide it.

Report version, reviewed SHA/tree, PR, draft/published Release status, serving identity and peeled remote tag identity. Keep preparation, merge, deployment and publication distinct, with explicit unverified steps.

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.