agentleFS
MrinankaMrinanka/aegiscontext/.claude/skills/ship/SKILL.md

ship

Skill1 starsChanged 12 days agoApache-2.0View on GitHub

Finish the step - update progress and decisions, commit, push the step branch and open a PR.

  • 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, 3 are distinctive, and 3 are 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.

  • 3

    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:

    Only if no issue from /verify is left to fix (if there is one, stop and list it):

    line 7
  2. Distinctive:

    add anything partial or deferred to Known issues (parked features go to spec §23)

    line 11
  3. Distinctive:

    add a 3–5 line session note

    line 13
  4. Very specific:

    Add each real decision from this step to docs/engineering/decision-log.md (next D-number, plus an index row) in the short form: Decision / …

    line 15
  5. Distinctive:

    Check that no file being committed holds a real-looking secret or a whole fake one.

    line 16
  6. Very specific:

    Run gh pr checks --watch and report each OS's result and the PR link.

    line 19

“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

Only if no issue from /verify is left to fix (if there is one, stop and list it):

  1. Update docs/engineering/progress.md:
    • tick the step
    • add anything partial or deferred to Known issues (parked features go to spec §23)
    • add new gotchas
    • add a 3–5 line session note
    • set Current focus to the next unticked step
  2. Add each real decision from this step to docs/engineering/decision-log.md (next D-number, plus an index row) in the short form: Decision / Why / Rejected alternative / Evidence. Use my reason where I gave one; if you don't know it, ask. Skip this if there were none.
  3. Check that no file being committed holds a real-looking secret or a whole fake one.
  4. Show me git status, then commit everything on the step branch as step <n>: <one-line summary>, ending with the Co-Authored-By line from the system attribution.
  5. Push the step branch (git push -u origin step-<n>; never force). Open a PR with gh pr create --base develop --head step-<n>, titled Step <n>: <name>, with a short body (what's built, decisions by D-id, known issues) ending with the PR attribution line.
  6. Run gh pr checks --watch and report each OS's result and the PR link. Don't merge, approve or close it; I merge.

Then remind me to merge, /clear, and start the next step from develop with /plan-step.

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.