agentleFS
epicsagasepicsagas/epic-harness/skills/ship/SKILL.md

ship

Skill20 starsChanged 2 months agoApache-2.0View on GitHub

Ship phase. Runs isolated integration test in a fresh worktree, creates a PR with full spec + audit report in the body, watches CI, and auto-fixes failures.

  • 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

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

  • 0

    Common

    Most of the 180 edited versions we read keep these.

  • 6

    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
  1. Very specific:

    CRITICAL: Run HARNESS_DIR=$(epic-harness path) first.

    line 8
  2. Distinctive:

    Gate: audit must have passed: If no audit report exists, invoke the audit skill before continuing.

    line 19
  3. Very specific:

    Run full build from scratch (cargo build --release / npm run build / etc.)

    line 25
  4. Distinctive:

    Run complete test suite

    line 26
  5. Distinctive:

    Run linter and formatter checks

    line 27
  6. Distinctive:

    Verify no uncommitted artifacts

    line 28
  7. Very specific:

    Gate: If isolated test fails → STOP.

    line 30
  8. Distinctive:

    Ensure all changes are committed (Conventional Commits)

    line 34
  9. Distinctive:

    If CI fails, diagnose and fix automatically.

    line 80

“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 — Ship It

CRITICAL: Run HARNESS_DIR=$(epic-harness path) first. NEVER use .harness/ in the project directory.

Process

Step 0: Prerequisites

Load the spec for PR content:

ls -t $HARNESS_DIR/specs/SPEC-*.md | head -1

Gate: audit must have passed. If no audit report exists, invoke the audit skill before continuing.

Step 1: Pre-ship Verification

1a. Isolated Integration Test Launch an agent with isolation: "worktree" to verify in a clean environment:

  • Run full build from scratch (cargo build --release / npm run build / etc.)
  • Run complete test suite
  • Run linter and formatter checks
  • Verify no uncommitted artifacts

Gate: If isolated test fails → STOP. "Fix with /go, then re-run /audit before shipping."

Step 2: Git Hygiene

  • Ensure all changes are committed (Conventional Commits)
  • Rebase on latest base branch if needed
  • Squash fixup commits if appropriate

Step 3: Create PR

gh pr create --title "<goal from spec>" --body "$(cat <<'EOF'
## Summary
<Goal from spec — what and why, not how>

## Spec
- Spec ID: SPEC-{timestamp}
- Requirements: R1, R2, ...

## Changes
<bullet list of key changes>

## Acceptance Criteria Verified
- AC1: ✅
- AC2: ✅

## Audit Report
<paste full Audit Report>

## Test Plan
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual verification done
EOF
)"

Register the PR in the merge-outcome ledger (orbit pipelines are picked up automatically; standalone ships need this one-liner):

epic-harness evolve record-pr <PR_URL> [--goal <goal_slug>] [--branch <branch>]

Step 4: CI Verification

gh pr checks <PR_NUMBER> --watch

If CI fails, diagnose and fix automatically. Retry up to 2 times.

Step 5: Report

## Ship Report
- Spec: SPEC-{timestamp} ({goal_slug})
- PR: <URL>
- CI: [PASS/FAIL/N/A]
- Ready to merge: [YES/NO]
- Action needed: <if any>

If inside /orbit: Return control to orbit — it will run evolve automatically.

If standalone: Suggest "Run /evolve to analyze this session."

Anti-Rationalization

ExcuseRebuttalWhat to do instead
"CI will catch it"CI doesn't catch everythingRun isolated test locally first
"The PR description doesn't matter"It's the permanent record of whyInclude spec + audit report
"I'll merge without CI"CI is a safety netWait for CI, fix failures

Evidence Required

  • Isolated test passed in clean worktree
  • PR created with spec + audit report in body
  • CI status checked (PASS, FAIL with fix, or N/A)
  • All Conventional Commits applied

Red Flags

  • Shipping without a PASS audit report
  • PR description that says "various fixes" or "updates"
  • Force-pushing to main
  • Merging with failing CI
  • PR body missing the Audit Report section

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.