Gstack Ship
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.
Install
$ agentstack add skill-merllinsbeard-merlin-skills-ship ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-merllinsbeard-merlin-skills-ship) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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//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:
Remote:
Verification:
Residual risk: Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: merllinsbeard
- Source: merllinsbeard/merlin-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.