ship
SolidShips finished work the way this repo accepts it — one signed Conventional Commit of explicit paths, the changelog/FEATURES/BACKLOG lifecycle, a PR, the deploy check when the merge would publish the site, the work file closed, one retro line. Use "commit this", "open the PR", "ship it", "merge". Never pushes or merges without a yes.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- assaio
- Repository
- assaio/assaio
- Created
- 2 months ago
- Last Updated
- today
- Language
- Go
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
ship
Ship a finished task — commit → push → open a PR (concise body) → queue the ticket's move to review when a pipeline is configured → watch CI to green → stop. Writes to the tracker only through safe-outputs requests. Never merges. Use this when work on a feature branch is done and ready for review, or invoke it manually as /ship.
ship
Git and deploy ritual behind an explicit green-light gate. Use for any commit/push/PR/deploy intent — "commit", "push", "open a PR", "ship it", "deploy" — or when work is finished and needs to leave the machine.
ship
Delivery route after coding work is complete and the user asks to ship, create a PR, or publish the branch. Run test, scope, and review gates; commit relevant files; push a non-default branch; then upsert the PR and available QA evidence. Unfinished work returns to its execution owner.