skills.rest
Dozyboy
DozyboyCOMMUNITY
Explore all skills by this author →
GitHub

hs:ship

Orchestrates a gated ship pipeline from branch verification through human approval to push and PR creation.

Updated Jul 19, 2026
Search Tags:#git#code review#pull request#github#release automation#gating#ci pipeline
One-click install
npx skills add https://github.com/Dozyboy/VSF --skill hs-ship-dozyboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hs:ship
Source: https://github.com/Dozyboy/VSF/tree/main/Day2_VSF/Demo1/harness/plugins/hs/skills/ship
Command: npx skills add https://github.com/Dozyboy/VSF --skill hs-ship-dozyboy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping a completed branch to a pull request involves many error-prone steps — merging the target branch, running tests, completing code review, verifying approval artifacts, updating changelogs, and pushing — and skipping any gate can land unreviewed or unverified code. This Skill orchestrates the entire gated pipeline so every prerequisite is checked before code reaches the remote. ## Core Features & Use Cases - Gated pipeline orchestration: Runs an 11-step pipeline covering preflight checks, target-branch merge, test delegation, code review, artifact verification, changelog generation, human confirmation, push, and PR creation. - Artifact gate enforcement: Verifies verification.json, review-decision.json (verdict must be exactly PASS), and plan-approval.json (with plan-hash drift detection) before allowing the PR stage. - Automated release hygiene: Generates changelog entries, version bumps, conventional commits, and structured PR bodies with linked GitHub issues — without prompting for content. - Use Case: After finishing a feature branch with passing tests and an approved plan, invoke the ship pipeline to merge origin/main, confirm review and verification artifacts, get a live human confirmation, push, and open a PR with a fully populated body. ## Quick Start Ship my current feature branch to main using the official mode with the full gated pipeline.

Frequently Asked Questions about hs:ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ship a feature branch to a pull request with gates?▼

Run the ship pipeline from your feature branch, optionally passing official or beta mode. It merges the target branch, runs tests and code review, verifies required artifacts, asks for live human confirmation, then pushes and creates the PR with gh.

What artifacts are required before creating a PR?▼

Three artifacts are required at the PR stage: verification.json with no FAIL checks, review-decision.json with verdict exactly PASS (PASS_WITH_RISK does not qualify), and plan-approval.json with verdict APPROVED and a matching plan hash.

Does the pre-push hook block a push when artifacts are missing?▼

No. The pre-push hook only hard-blocks destructive pushes to protected branches and detected secrets; a missing receipt only produces a warning. Presence is truly enforced at the PR stage and by the remote receipts-gate, so the pipeline stops manually on missing artifacts.

Can I skip tests when shipping a branch?▼

Yes, pass --skip-tests to reuse an existing verification.json, but only when it was produced in the current branch state. A stale artifact from an earlier commit passes the gate on evidence that no longer matches the diff, so re-run tests if HEAD moved.

What happens when the code review verdict is PASS_WITH_RISK?▼

The pipeline stops, because the ship gate requires a verdict of exactly PASS. You are asked to choose between fixing and re-reviewing, accepting the risk (which blocks the ship), or cancelling the pipeline entirely.

Why does the plan-approval check fail after editing the plan?▼

Editing the plan after approval changes its hash, causing a drift failure on the plan-approval check. Re-approve the plan via plan_approval.py to regenerate the artifact with the current hash before shipping.

Related Skills

Explore More Software Engineering Skills→
icliniciclinic
9

completing

Finalize features by merging, creating a PR, or summarizing completion.

Official
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

land-and-deploy

Merge pull requests, monitor CI, deploy to production, and verify health with canary checks.

Community
Intermediate
jungzunajungzuna
2

haejwo-plan

Validate software development plans through independent reviewer critique and consensus.

Community
Advanced
bnfergusonbnferguson

gh-stack

Manage stacked branches and dependent pull requests with the gh-stack GitHub CLI extension.

Community
Advanced