ship

Solid

Ship a feature branch end-to-end: merge target → test → review → version/changelog → commit → push → PR, then drive CI green and hand off the PR. Use when ready to land a branch on main/master (official) or dev/beta (beta). Merge is opt-in — a bare ship stops at a green PR; it merges only with --auto or --merge. Stops on test failures, critical review issues, or major version bumps.

Code & Development 2 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
16
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Ship ## What this skill is — and isn't | Skill | Question it answers | Output | |---|---|---| | `vd:cook` | "Execute the plan." | Code, tests, plan status | | **`vd:ship`** | **"The branch is ready — open the PR and take it green."** | **PR URL on green CI; merge only with `--auto`/`--merge`** | Ship **prepares** a branch to land: merge target, test, review, version, PR, then drives CI to green and clears review comments — and by default **hands the PR back to you unmerged**. Merging is opt-in (`--auto` or `--merge`, or an explicit "merge" / "land it"); see **Hard rule 0**. It does not implement features and does not redesign on the fly. If tests fail or review surfaces a real bug, **stop** and kick back to `vd:cook` — don't paper over issues to keep the pipeline moving. ## Ship modes | Mode | Target branch (auto-detected) | Use for | |------|-------------------------------|---------| | `official` | `main` / `master` | Production code merge | | `staging` | `staging` / `uat` / `release/x.y.z` | Pre-prod, QA validation | | `beta` | `dev` / `development` / `beta` | Active dev / preview | Add `--release` to any mode to also cut a GitHub release. Tag style adapts to the mode: | Mode + `--release` | Tag | GitHub release | |--------------------|-----|----------------| | `official --release` | `vX.Y.Z` | Stable (latest) | | `staging --release` | `vX.Y.Z-rc.N` | Prerelease | | `beta --release` | `vX.Y.Z-beta.N` | Prerelease | If an auto-release tool is detected (`goreleaser`...

Details

Author
vanducng
Repository
vanducng/skills
Created
2 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

skills

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

ship

Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'. Add --verify to trigger an adversarial verifier wave on the diff before a human reads the PR.

45 Updated today
griffinwork40
Code & Development Listed

ship

Push a committed feature branch, open a PR, watch CI, and (only on explicit confirmation) squash-merge and clean up. Use when the user says "ship this", "push and open a PR", "is CI green yet", or asks to merge a PR that's already open. Assumes the branch is already committed — this skill does not stage or commit anything. Does not require ending at a merge: an open, CI-green PR is a valid stopping point.

1 Updated 1 weeks ago
RonenMars
Code & Development Listed

ship

Push a committed feature branch, open a PR, watch CI, and (only on explicit confirmation) squash-merge and clean up. Use when the user says "ship this", "push and open a PR", "is CI green yet", or asks to merge a PR that's already open. Assumes the branch is already committed — this skill does not stage or commit anything. Does not require ending at a merge: an open, CI-green PR is a valid stopping point.

0 Updated 1 weeks ago
RonenMars