gstack-ship
Skill1 starsChanged 6 months agoMITView on GitHub
Merlin-adapted ship gate for spec-kit/create-goal work. Use when implementation and QA evidence are ready and the user asks to package, commit, push, release, or deploy.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- robertkarl/rkstacktheir own version, first seen Oct 20, 2026
- sagnikmitra/skillstheir own version, first seen Jun 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- sagnikmitra/skills★ 1same name
- robertkarl/rkstack★ 0same name
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.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brainstormingSkill
- create-goalSkill
- diagnoseSkill
- grill-with-docsSkill
- install-merlin-skillsSkill
- merlin-skills-routingSkill
- playwright-cliSkill
- playwright-skillSkill
- gstack-qaSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-cliSkill
- speckit-constitutionSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- tddSkill
- to-prdSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
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
- Distinctive: line 13
Use when the user says the work is ready to ship, asks to create a PR, push changes, tag a release, or deploy.
- Very specific: line 15
Do not use when implementation is still incomplete.
- Distinctive: line 29
Before mutating release state, verify:
- Distinctive: line 38
If any gate fails, stop and report the blocker.
- Distinctive: line 43
Run the minimum relevant checks again if they are cheap.
- Distinctive: line 44
Update release metadata only when appropriate for the repo.
- Distinctive: line 45
Commit with explicit path selection.
- Distinctive: line 47
Verify the remote state after pushing or releasing.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
gstack-ship
Ship only after the spec/goal has proof. This skill is adapted from gstack ship, but it is standalone: do not call gstack runtime helpers, telemetry, review specialists, gbrain, or deploy automation unless the repo already owns that command.
When To Use
Use when the user says the work is ready to ship, asks to create a PR, push changes, tag a release, or deploy.
Do not use when implementation is still incomplete. Route to gstack-qa, tdd, or diagnose first.
Inputs
Inspect, in order:
- User's newest ship instruction.
- Current branch, git status, and git diff.
- Active
specs/<feature>/GOAL.md,tasks.md,plan.md, andspec.mdwhen present. - Latest QA report or verification evidence.
- Repo instructions in
AGENTS.md,README.md, release docs, CI config, package scripts, and deploy docs.
Ship Gate
Before mutating release state, verify:
- The work matches the active spec/goal or the user explicitly scoped a diff-only ship.
- Relevant tests and checks pass.
gstack-qaevidence exists or the user explicitly waived QA.- The diff contains no unrelated changes you would accidentally commit.
- Version, changelog, release notes, and docs are updated when the repo's release policy requires them.
- The user has allowed the requested side effect: commit, push, PR, tag, release, merge, or deploy.
If any gate fails, stop and report the blocker.
Workflow
- Summarize the exact diff that will ship.
- Run the minimum relevant checks again if they are cheap.
- Update release metadata only when appropriate for the repo.
- Commit with explicit path selection. Never use
git add .. - Push, tag, create PR, create GitHub Release, merge, or deploy only when requested or clearly part of the current repo's established ship flow.
- Verify the remote state after pushing or releasing.
Output
End with:
Ship Result: shipped | ready-not-pushed | blocked
Commit: <sha or none>
Remote: <branch/tag/pr/release/deploy URL or none>
Verification: <commands and evidence>
Residual risk: <short list or none>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
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.