agentleFS
DenchHQDenchHQ/ironclaw/skills/gstack/ship/SKILL.md

ship

Skill1.7k starsChanged 7 months agoMITView on GitHub

Release engineering — sync main, run tests, audit coverage, push branch, open PR. Bootstraps test frameworks if needed. One command from "code complete" to "PR ready for review".

  • Commits and pushes

194 other projects use a version of this.

Trending

Quiet since February.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the DenchHQ/ironclaw repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about DenchHQ/ironclaw

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

Used with

Projects with it also use ios-sync, open-gstack-browser and 8 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

  • 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

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

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 8

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

    If conflicts: resolve them.

    line 32
  2. Distinctive:

    All tests must pass: If tests fail:

    line 47
  3. Distinctive:

    Read the failure output

    line 49
  4. Distinctive:

    If stuck after 3 attempts, ask the user

    line 52
  5. Distinctive:

    Check test coverage for files changed in this branch:

    line 58
  6. Distinctive:

    If missing tests, write them before proceeding (unless the user explicitly opts out).

    line 78
  7. Distinctive:

    Labels: If applicable (bug, feature, refactor)

    line 96
  8. Distinctive:

    After the PR is approved, use land-and-deploy to merge and deploy.

    line 127

“Common” is measured: kept by at least 6 in 10 of the 179 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 — From Code Complete to PR

You are the release engineer. Take this branch from "done coding" to "PR ready for review."

Related skills: review | land-and-deploy | qa


Step 0: Detect Base Branch

  1. gh pr view --json baseRefName -q .baseRefName
  2. Fallback: gh repo view --json defaultBranchRef -q .defaultBranchRef.name
  3. Fallback: main

Step 1: Sync with Base

git fetch origin <base> --quiet
git merge origin/<base> --no-edit

If conflicts: resolve them. If complex conflicts, ask the user.


Step 2: Run Tests

# Detect and run the project's test suite
npm test          # Node.js
bundle exec rake  # Ruby
pytest            # Python
go test ./...     # Go
cargo test        # Rust

All tests must pass. If tests fail:

  1. Read the failure output
  2. Fix the failing test (if it's a real bug, fix the bug)
  3. Re-run tests
  4. If stuck after 3 attempts, ask the user

Step 3: Coverage Audit

Check test coverage for files changed in this branch:

git diff origin/<base> --name-only

For each changed file, check if corresponding tests exist. Flag gaps:

COVERAGE AUDIT
═══════════════════════════════════════
Changed files:     12
With tests:        9
Missing tests:     3
  - src/services/billing.ts (new service, no tests)
  - src/utils/formatter.ts (new utility, no tests)
  - src/api/webhook.ts (new endpoint, no tests)
═══════════════════════════════════════

If missing tests, write them before proceeding (unless the user explicitly opts out).


Step 4: Push Branch

git push -u origin HEAD

Step 5: Create PR

Generate a PR with:

  • Title: Concise description of the change
  • Body: What changed, why, and how to test
  • Labels: If applicable (bug, feature, refactor)
gh pr create --title "..." --body "..."

Step 6: Post-Ship Checklist

  • Tests pass
  • Coverage gaps addressed or acknowledged
  • No uncommitted changes
  • PR description is clear
  • Documentation updated (suggest document-release if needed)

Output

SHIP REPORT
═══════════════════════════════════════
Branch:           feature/my-feature
Base:             main
Tests:            42 pass, 0 fail
Coverage:         +9 new tests
PR:               github.com/org/repo/pull/123
═══════════════════════════════════════

After the PR is approved, use land-and-deploy to merge and deploy.

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.