From silver-bullet
Runs phase-level shipping gates: branch/PR readiness, CI status, docs traceability, and handoff. Use before creating a PR or merging a phase.
How this skill is triggered — by the user, by Claude, or both
Slash command
/silver-bullet:silver-ship <phase or ship scope><phase or ship scope>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
SB-owned phase shipping handles branch/PR readiness, CI status, deployment
SB-owned phase shipping handles branch/PR readiness, CI status, deployment readiness, docs traceability, and handoff.
This is phase-level ship, not milestone release. Use silver:release for
versioned publication.
UAT scope: uat-gate.sh runs only when silver:release is invoked — phase
PRs via silver:ship do not require .planning/UAT.md even when
.planning/SPEC.md has acceptance criteria. Run /silver:release (or invoke
silver:release explicitly) when milestone-level acceptance testing is required
before publication.
Write or update the ship section in .planning/STATE.md, current phase
SUMMARY/VERIFICATION, or a PR description draft.
SILVER BULLET > SHIP.silver:verify;silver:review;silver:secure;silver:validate where the workflow requires it;silver:domain-audit where specialized packs were selected by
silver:quality-gates, review, verification, DevOps, or release scope;verify-tests — mandatory before any delivery. verify-tests is in the
required_deploy list, so the completion-audit deploy gate blocks
gh pr create / gh release create / deploy until a fresh verify-tests
run is recorded. Run it here even when the suite was run earlier in the phase,
so the recorded freshness marker reflects the shipped tree.silver:branch-finish on non-main branches.Ship passes only when the branch/PR action is clear, required gates are fresh, and the user can see exactly what is being delivered.
npx claudepluginhub alo-exp/silver-bullet --plugin silver-bulletGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.