shipping-workflow

Review, fix, and complete a finished code slice via local merge or change request.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/hacker-cb/claude-code-plugins --skill shipping-workflow-hacker-cb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipping-workflow
Source: https://github.com/hacker-cb/claude-code-plugins/tree/main/plugins/hcb-dev/skills/shipping-workflow
Command: npx skills add https://github.com/hacker-cb/claude-code-plugins --skill shipping-workflow-hacker-cb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Finished work often ships without a consistent local review, leaving stale references, uncommitted fixes, and unchecked reviewer coverage. This Skill enforces a repeatable completion pipeline so every finished slice is reviewed, fixed, and merged or turned into a change request under explicit authorization. ## Core Features & Use Cases - Branch normalization and base refresh: Renames placeholder branches, fetches the parent and diff-base, commits the change, and sweeps for orphaned references to deleted or renamed paths. - Local multi-source review with a coverage gate: Hands the slice to a multi-review round, applies and commits the resulting fixes, and stops before completing if any reviewer source has an actionable coverage gap. - Completion by mode: Merges locally into the parent branch with git alone, or hands off to a change-request driver such as a GitHub PR workflow with merge strategy and authorization threaded through. - Use Case: After finishing a feature branch, say "ship this" and the Skill rebases onto the parent, runs the review round, commits the fixes, verifies coverage, and opens a PR or merges locally. ## Quick Start Tell the AI to ship the finished branch using the shipping-workflow skill, choosing a local merge or a pull request as the completion mode.

Frequently Asked Questions about shipping-workflow

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

FAQPage Schema
How do I ship a finished feature branch with a local review first?▼

Invoke the shipping workflow on the finished branch: it normalizes the branch name, rebases onto the parent, runs a multi-source local review, commits the fixes, and then completes by merging locally or opening a change request.

What is the difference between local mode and request mode?▼

Local mode merges the slice into its parent branch using git alone with no network writes. Request mode hands off to a change-request driver such as the GitHub PR workflow, passing the base, merge strategy, and merge authorization.

When should I use this instead of opening a pull request directly?▼

Use it when finished work has not been reviewed locally yet. Entering a PR driver directly skips the local reviewers and the coverage gate this workflow enforces before any change request is opened.

What happens if a reviewer source has a coverage gap?▼

The workflow stops before completing and reports the gap in a review coverage section with a blocking ask. Completion proceeds only after the user explicitly approves, in both local and request modes.

Can it run when a project forbids committing or pull requests?▼

Yes. Project rules outrank the workflow: it follows the repository's commit or change-request restrictions, names the step it skips, and flags conflicts unless a rule blocks correct work outright.