agentleFS
Sign inStart free
AWSKnown publisherawslabs/loom/.claude/skills/ship/SKILL.md

ship

Skill199 starsChanged 4 months agoApache-2.0View on GitHub

Finalize dev work on an issue branch — update docs, push, and open a PR.

  • Commits and pushes

We split this skill into the rules it gives an agent

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run git log main..HEAD --oneline to see all commits on this branch.

    line 20
  2. Distinctive:

    Run git status to confirm the working tree is clean.

    line 22
  3. Very specific:

    Run gh issue view $ARGUMENTS --json title,body,labels,number to get the issue title and number.

    line 26
  4. Very specific:

    Search for all SPECIFICATIONS.md files in the repository using Glob (/SPECIFICATIONS.md).

    line 32
  5. Very specific:

    Search for all README.md files in the repository using Glob (/README.md).

    line 34
  6. Very specific:

    Create a pull request using gh pr create.

    line 57

“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 Issue

Finalize development work on a feature branch: update documentation, push, and submit a pull request.

Input

$ARGUMENTS must be a GitHub issue number (e.g. 78). If missing or non-numeric, ask the user for the issue number.

Step 1: Verify Branch State

Confirm that you are on a feature branch (not main). If on main, abort and tell the user to switch to the feature branch first.

Run git log main..HEAD --oneline to see all commits on this branch. There must be at least one commit. Display the commit list to the user.

Run git status to confirm the working tree is clean. If there are uncommitted changes, warn the user and ask how to proceed.

Step 2: Fetch Issue Details

Run gh issue view $ARGUMENTS --json title,body,labels,number to get the issue title and number.

Also check if a matching markdown file exists under tmp/issues/ by looking for files that start with a zero-padded version of the issue number (e.g. issue 78 maps to a file starting with 078-). If the file exists, read it to understand the requirements for documentation updates.

Step 3: Update Documentation

Search for all SPECIFICATIONS.md files in the repository using Glob (**/SPECIFICATIONS.md). Update each relevant file with the latest design decisions from this branch's changes. Use git diff main..HEAD to understand what changed.

Search for all README.md files in the repository using Glob (**/README.md). Update each relevant file with the latest implementation details. Ensure no sensitive or account-specific information is included — no ARNs, account IDs, tokens, secrets, or endpoint URLs.

Step 4: Commit Documentation Updates

Stage and commit all documentation changes:

git add -A
git commit -m "docs: update specifications and readme for issue #$ARGUMENTS

Co-Authored-By: Claude <noreply@anthropic.com>"

Step 5: Push and Create Pull Request

Display the final commits with git log main..HEAD --oneline for the user to review.

Push the branch to the remote:

git push -u origin HEAD

Create a pull request using gh pr create. Derive the PR title and body from the issue and the work done:

gh pr create --title "<semantic-prefix>: <short description>" --body "$(cat <<'EOF'
## Summary
<2-4 bullet points describing what this PR does>

## Test Plan
<bullet list of how the changes were tested>

Closes #$ARGUMENTS

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

The PR body must include Closes #<issue-number> so the issue is automatically closed when the PR is merged.

Display the PR URL to the user.

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★ 138ksame name
    2. rtk-ai/rtk★ 85ksame name
    3. simstudioai/sim★ 30ksame name
    4. millionco/react-doctor★ 15ksame name
    5. BuilderIO/agent-native★ 7.4ksame name
    6. fallow-rs/fallow★ 5.1ksame name
    7. plugin87/ux-ui-agent-skills★ 3ksame name
    8. ShenSeanChen/waku-agent★ 2ksame name
    9. DenchHQ/DenchClaw★ 1.7ksame name
    10. DenchHQ/ironclaw★ 1.7ksame 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

    • ayudaySkill

      unfreeze

      Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits".

      Also in 21 projects that use this

  • In this repository3 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.

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