ship
Solidverify every release precondition, abort on any fault, then hand back the bump, push and promote steps
Install
Quality Score: 82/100
Skill Content
Details
- Author
- MaisonDeVolonte
- Repository
- MaisonDeVolonte/construct
- Created
- 1 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
ship
Ship a Pacer release using the install-first, single-gate flow. Use when the maintainer asks to release / ship / cut / publish a version, or — after a local install they've reviewed — to land and release the current work. Covers the version-bump + release-notes gate, landing the PR, and the backgrounded tag → watch → verify. Do NOT start a release mid-work: it only begins once the work is done AND approved (either up front — "…and release it" — or at the post-install gate). The mechanical half is `bin/ship.sh`; the human process + one-time secret setup is `docs/releasing.md`.
ship
Release behind verify gates — run the tests, read the diff, then a staged rollout with a rollback plan.
ship
End-to-end shipping — version bump, changelog update, tag, GitHub release, deploy, and post-deploy verification. Validates PR goal, checks, review state, and risk. Refuses admin bypasses or force options against main.