agentleFS
Sign inStart free
vishalguptaxvishalguptax/agent-engineering-kit/.claude/skills/ship/SKILL.md

ship

Skill0 starsChanged 24 days agoMITView on GitHub

Prepare the verified, reviewed change for delivery - final checks, focused commits with good messages, and a pull request description. Only when the user explicitly asks to commit, push, or open a PR.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 180 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

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

    Do what the user asked for when starting this skill: prepare commits (the default), push, or open a PR.

    line 9
  2. Distinctive:

    If the project isn't a git repository, stop: say so and summarize the changed files and the suggested commit message instead.

    line 11
  3. Distinctive:

    Push or open a PR only if I asked for it: Never force-push, rewrite shared history, or merge without explicit permission.

    line 17

“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 — commit and PR

Do what the user asked for when starting this skill: prepare commits (the default), push, or open a PR. Never more than that. The project's instructions (AGENTS.md, CLAUDE.md), including its Workflow Preferences section if there is one, take priority over the steps below.

If the project isn't a git repository, stop: say so and summarize the changed files and the suggested commit message instead.

  1. Gate: confirm the verify-change skill passed and the review found no open must-fix issues in this session (code review plus the reviewer agents that apply: test-analyzer, silent-failure-hunter, security-reviewer, frontend-reviewer). If not, run them first.
  2. Inspect: git status and git diff. Make sure no secrets, env files, build output, debug code, or unrelated changes are included. Exclude anything unrelated and tell me.
  3. Commits: group changes into focused commits (one concern each). Follow the project's commit convention (Workflow Preferences, then git log and CONTRIBUTING); default to Conventional Commits (feat:, fix:, refactor:, test:, docs:, chore:). Messages explain why, not just what.
  4. PR description (use the project's PR template if one exists): summary and motivation; approach and key decisions; how it was tested (commands and results, screenshots for UI); risks, rollout notes, follow-ups. Link the plan in .agent-kit/plans/ (or where the Workflow Preferences put plans) if there is one.
  5. Push or open a PR only if I asked for it. Never force-push, rewrite shared history, or merge without explicit permission.

Download now (ZIP)

  • Other versions193 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 193

    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.6ksame name
    6. fallow-rs/fallow★ 5.3ksame name
    7. nightly-labs/openbot★ 4.4ksame name
    8. puncsky/system-design-and-architecture★ 3.6ksame name
    9. plugin87/ux-ui-agent-skills★ 3.1ksame name
    10. ShenSeanChen/waku-agent★ 2ksame name

    183 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

    • 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

    • +2 more from ShreyRavi
  • In this repository8 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