Index of every page on this site: llms.txt
All skills
garrytan avatar

/ship

@8586794 official
by Garry Tangarrytan/gstack142k stars
20,987
Run it yourself

Ship it: merge the base, run tests, review the diff, bump VERSION and CHANGELOG, push and create a PR. Use for: ship it, create a pr, push to main. (gstack)

Use this Skill: https://skilld.dev/gh/garrytan/gstack/ship

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

DRIVER.md

≈3.1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

<!-- AUTO-GENERATED from ship/DRIVER.md.tmpl — do not edit directly --> <!-- Regenerate: bun run gen:skill-docs -->

/ship driver: run /ship from a parent agent

Read this, not ship/SKILL.md, when a parent agent runs /ship (SESSION_KIND: unattended). Commands live in <root>/bin/ (<root> holds ship/); run each with the GSTACK_LAUNCH assignments your installer printed (. <its GSTACK_LAUNCH_FILE>), never export $(...), env, printenv or a bare set in a tool fence.

Rules. Each phase below is one call: gstack-ship-phase run --dir <run dir> --phase <n> --record <rec> -- <cmds> runs its bins, reads, dispatches and waits, returning only result lines and reader outputs verbatim. The model keeps only judgment, fixes, CHANGELOG, PR prose, gates, the report. STOP: (exit 3) means nothing after it ran; NEXT: names the next act. Read a section only when a phase or the list below sends you, never up front. A STOP or decision this file does not cover: read ship/SKILL.md at that step, finish there, come back. Unattended, take a question's recommended option (log it); gate dispositions and approvals stay pending and end the run, except gstack-no-stop. Keep a record (--record): write its six headings at Phase 1, fill each per phase: Checks (Phases 2-4: lanes, pregate, evals, Coverage:, the plan checks, Exploratory QA:, Scope Check:), Decisions (any phase: questions and answers, verbatim), Reviews (Phases 3-5: the plan line, start tokens, Pre-Landing Review:, Gate edits:, the reviewed tree), Release (Phases 5-7: version, CHANGELOG, commits), Documentation (Step 14.5) and Next steps (every phase: the next act).

Reviewers are the sections' own. Every reviewer brief, its severity and confidence rules and gates come from its section verbatim; this file never shortens a reviewer's brief. A blocking reader's prompt is its gstack-review-dispatch render file, unchanged; its findings reach merged.jsonl only via collect; judge refuses a drop or downgrade. Audit readers (Steps 7, 8, 14.5) cannot block: low effort on AUDIT_MODEL:, 14.5 once; findings go to the PR body.

Calls. One pass with no fixes is 9 calls: Phases 1-8 and the report; at most 12 with a STOP's section read or fix-check, plus a keep-alive per 200 s waited under ~80 min (longer: end the turn on one wait; no 10-15 min polls).

Budget: observe. gstack-ship-budget start --mode observe only records: each program ends with gstack-ship-budget note --step <last step> --reading R --credits C --record <rec>, R and C read in it (Capy: cost.tokens, cost.credits). No check per step, no reservation, no meter-only call, no handoff; under --token-cap a note past the cap prints verdict=stop, the one stop check on spend. A dispatching program passes --dispatched-at <R> --dispatched-credits <C> --readers <n> (BEFORE).

Waits. No call waits past 200 s: a program returns what still runs 200 s after its first line; the next call resumes the poll. Lanes, pregate, finish run in background; after a restart, rerun the same command. Never end the turn while readers run. A small waiting child saves nothing. Past 100 minutes the run stops: STOP: past 100 minutes, state in stop.json. Returns: ≤32 KB per program; split longer reads at headings, each byte once, before first use: phase programs end with gstack-ship-parts next --run <run dir> --phase <n+1> --room <32000 - its output>; on NEXT: parts run it alone.

One program per pass. Each review pass, Step 11 and the Step 14.5 audit is one program, and the parent makes no other call while it runs: (1) gstack-review-dispatch pass: gstack-review-plan --base <base> with Step 9's plan flags, then its staged manifest (Step 14.5: one reader, docs); (2) gstack-review-log --start <skill> once per row the step logs; (3) BEFORE; (4) sent (BRIEF_MISMATCH voids it), then one subagent per reader on its rendered file; (5) a poll until every reader settles (status done or failed, or a final summary; a fresh idle has not run); (6) note with the reading pair; a later batch (the Red Team, on the specialists' collected lines) repeats (3)-(6); (7) the collect: return only each reader's final output and status, via collect; it never walks the dispatch steps call by call.

1. Load: Step 0

Install check, this file.

2. Preflight, tests, evals and reads: Steps 0.9, 1, 2, 3, 4, 5, 6, 6.5, 10

gstack-ship-budget start --record <rec> --mode observe [--token-cap <n>] --reading R --credits C, then gstack-ship-preflight --base <base> --run <run dir name> --lane <label>=<test command>.... CARRY: carried ends the run on its GSTACK_RESULT: line. ship_lanes_from: push early (sections/tests.md#ci-carry). A lane passes on tests_ran: N with exit 0; 0 is ZERO-RUN (failed); unknown is count unavailable. In-branch failures stop; after a repair rerun --tests-only. requires-remote needs gstack-pregate clear before Step 18. Changed prompts, templates, judges or eval harness: start the eval selector and pre-merge command (detached past 30 min); else record evals: none affected. Step 6.5 runs only if gstack-greptile-early detect finds Greptile. Then gstack-ship-preflight --audit --base <base> --out <run dir> writes the diff once (CONTEXT:) and the TODOS.md items on touched paths (TODOS:); prints the coverage map, plan candidates and READER: coverage=<needed|none> plan=<needed|none>; read a section only when its reader is needed. Never read TODOS.md or the full diff into the parent. A PERSIST: hint never replaces Step 9.

3. Audits and review: Steps 7, 8, 9, 9.1, 9.2, 9.2.1

One program: the audit readers READER: names (Step 7 from sections/test-coverage.md, Step 8 from sections/plan-completion.md, each run as written; Step 7 may write tests, so it settles first), 9.2.1's Reads only and the pass (above): Steps 9-9.2 from sections/review-army.md as written. Coverage: and Step 8's line come from --audit when no reader ran.

4. Judgment: Steps 8.1, 8.2, 9.3, 9.4 and Step 11

Step 8.1, 9.2.1's probes, 8.2 (Scope Check:) on the todos and commits files, then the core checklist, Steps 9.3, 9.4 and the repeat decision as written (JUDGMENT: ok before any fix), fixes and persistence in one program. Prints Pre-Landing Review:, Gate edits:. NEXT: stop stops; full or scoped: one program runs the failing test, fix, --tests-only and Phase 3, each gated (diffBase RANGE_BASE on full only; scoped fix-check: Step 3.5); fix-check: the pass with fixCheck: {fix_list, hunks, tests, callers}; done or voices: that program runs Step 11 from sections/adversarial.md as written (above), only the voices the last full-pass plan lists (none: ADVERSARIAL: skipped (review plan)).

5. Voices, bind and version: Steps 11, 11.5, 12

Judge the voices; missing outside coverage is unavailable, never clean; queued fixes rerun Phases 3-4. Then gstack-review-dispatch verify (VERIFY: clean) and gstack-review-read: the final Step 9 and 11 native rows (or CURRENT freshness after a planned skip) agree on one tree; save it (or --stop's) and base <b>. Then gstack-ship-release version --base <base> [--bump micro|patch] --why '<line>'; MINOR, MAJOR, BUMP_ANSWER_REQUIRED: approvals; VERSION: skipped|kept: no write.

6. Notes and documentation: Steps 13, 14, 14.5

Step 13: one user-facing entry from the commits file where NEXT: says; gstack-prose-lint <it> --base origin/<base> --gate until PROSE_LINT: ok. Step 14: TODOS.md deferrals and completions, edited from the todos file. Step 14.5, every ship: read sections/documentation.md and run its audit as written, as one program (above), then gstack-ship-receipt docs-caps --base <base>; print Documentation:. One re-audit at most.

7. Release: Steps 15, 16, 17

Commit bisectably; gstack-ship-release finish --base <base> --reviewed-tree <t> --reviewed-base <b> --docs-post <post> --lane ... [--build <cmd>] --trailer '<t>' [--plan <line>]: PLAN:, ROUTE:, DOCS:, EVIDENCE: (FRESH; STALE or MISSING reruns once), PREGATE:; print them, the last Gate edits: and each tests_ran. Then gstack-ship-release push --branch <branch> [--gate-open <n>]: REDACT_PREPUSH:, SEALED:, GUARDS:, PUSH: last: pushed|already_pushed|failed. EVIDENCE: DEFERRED: the accept NEXT: names; final-head repo gates run with CI. Unattended, push defers the pre-push offer; else its STOP runs Step 17's guard block (HOOK_STATE:, HOOKS_IN_GIT_DIR:, PREPUSH_PROMPTED:). Never force-push.

8. Publish: Steps 18, 19, 19-C, 20, 21, 22

  • Step 18: the open-PR lookup; a plain v<NEW_VERSION> title (gstack-plain-title check). UNATTENDED_SHIP: with no open PR at HEAD takes Step 18-H.
  • Step 19 body: plain opening sentences, then sections sections/pr-body.md lists, led under CAPY_PR: on (Step 19-C) by What changed, Why and Blast radius; Agent notes last (receipt, gstack-approvals render --plan, REVIEW_LOOP:). gstack-prose-lint <top> --sections 'Why,Summary,Blast radius' --gate; gstack-issue-links; gstack-review-scope summary --since "$REVIEW_SINCE" --run <dir> && gstack-ship-receipt write --pr <n> --base <base> --gate @<f> --pregate <f> --issues @<f> --review-loop @<f> --docs @<f> --budget-record <rec> [--review-exclude <d>] [--review-targeted @<f>] --body <body>; gstack-post pr-body and pr-title (new PR: host PR tool; draft while a gate finding is open). SHIP_RECEIPT: opens your report.
  • Step 20: a metrics row via gstack-review-log.
  • Step 22: gstack-ship-budget close --reading R --credits C (report BUDGET_FINAL:, BUDGET_TIMELINE:, any METER: line), then gstack-ship-receipt result --pr <n>: GSTACK_RESULT: skill=ship status=complete head=<sha> run=<dir>. Under a merge queue, gstack-ship-queue ready --pr <n> [--screen|--no-screen] at the pushed head; paste its output.

Where each STOP sends you (paths under <root>/ship/)

  • merge conflicts: SKILL.md#step-3-merge-the-base-branch-before-tests
  • NEXT: carry route: SKILL.md#step-1-pre-flight
  • DISTRIBUTION: candidates=: SKILL.md#step-2-distribution-pipeline-check
  • APPLE: with a store ask: sections/apple-release.md#apple-app-store-release
  • pregate fail or incomplete: sections/tests.md#step-5-run-tests-on-merged-code
  • a failed or zero-run lane: sections/tests.md#test-failure-ownership-triage
  • a red eval or a failed free-suite shard: sections/measure.md#measure-then-fix-loop-a-red-paid-eval-or-a-failed-free-suite-shard
  • Greptile found: sections/greptile-early.md#step-65-early-greptile-pr-after-the-free-tests-pass
  • Step 10 with a PR: sections/greptile.md#step-10-address-review-bot-comments-if-pr-exists
  • coverage below target, a failed audit: sections/test-coverage.md#step-7-test-coverage-audit
  • plan items NOT DONE or UNVERIFIABLE: sections/plan-completion.md#gate-logic
  • NEXT: stop: sections/review-army.md#decide-whether-to-repeat-step-9
  • a REVIEW_SCOPE_* refusal, the review-log row: sections/review-army.md#step-94-fix-first-and-persistence
  • a required probe not passed: sections/review-army.md#step-921-exploratory-qa-before-fix-first
  • native adversarial incomplete, queued fixes: sections/adversarial.md#finish-the-adversarial-phase
  • Step 11.5 mismatch: SKILL.md#step-115-bind-the-reviews
  • a version STOP: SKILL.md#step-12-version-bump-auto-decide
  • Documentation: blocked or a DOCS_CAP: over: sections/documentation.md#blocked-recovery
  • finish: changed since review: SKILL.md#2-choose-the-change-route
  • finish: documentation inputs changed: SKILL.md#3-resolve-documentation-freshness
  • finish: build, lane or pregate STOP: SKILL.md#4-verify-the-frozen-candidate
  • a push STOP: SKILL.md#step-17-push
  • unattended, no open PR at HEAD: sections/handoff.md#step-18-h-handoff-without-a-pr-automation-lanes
  • a receipt write or gstack-post refusal: sections/pr-body.md#compose-the-body-then-publish-through-gstack-post
  • verdict=stop or DELEGATE:: sections/budget-handoff.md#budget-and-context-handoff-read-when-a-cap-is-set-or-verdictdelegate-prints
  • QUEUE_RECEIPT_STALE: ../docs/ship-policy.md#ship-before-ready

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

3 alertstoday4 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    The skill is a comprehensive automation tool for software development release cycles, including code merging, automated testing, version management, and App Store distribution. It relies on a local 'gstack' binary toolset and integrates with reputable platforms like GitHub, GitLab, and Apple. The skill incorporates security best practices such as credential redaction guards and explicit instructions to isolate untrusted data from project plans and PR bodies. All identified patterns are aligned with the skill's primary purpose and utilize trusted organizations and services.

  • Sockettoday

    1 alert: gptMalware

  • Snyktoday

    Risk: CRITICAL · 3 issues

  • Runlayer8mo

    1/1 file flagged

Signed by skilld at 8586794. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated yesterday
What it can do
Runs commands Reads files Edits files Network
preamble-tier
4
version
1.0.0
triggers
[
  "ship it",
  "create a pr",
  "push to main"
]
All 10 allowed tools
BashReadWriteEditGrepGlobAgentAskUserQuestionWebSearchBash(~/.claude/skills/gstack/bin/gstack-skill-load:*)

README badge

README badge for garrytan/gstack/ship

Orchestrates a complete release workflow: detects the base branch, merges it, runs tests, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates a pull request. Built on the gstack tool and triggered by phrases like "ship it" or "create a PR".

Generated from the current SKILL.md.

What does this skill do?
The ship skill automates the full release workflow: detect and merge the base branch, run tests, review the diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Invoke it when code is ready to ship.
When should I invoke this skill instead of pushing manually?
Invoke ship proactively whenever the user says code is ready, asks to deploy, wants to push code up, or requests creating a PR. Do not push or create a PR directly — the skill handles the entire workflow.
What tools and permissions does this skill use?
The skill uses Bash, Read, Write, Edit, Grep, Glob, Agent, AskUserQuestion, and WebSearch. It requires git access and permission to commit, push, and create pull requests.
Does this skill work in plan mode?
Yes. In plan mode, treat the skill file as executable instructions and follow it step-by-step. The first AskUserQuestion call satisfies plan mode's end-of-turn requirement. Do not call ExitPlanMode until the workflow completes.

Generated from the current SKILL.md. These answers refresh after source changes.