ship

Orchestrate GitHub issue-to-PR workflows with branch creation, review, and auto-merge setup.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill ship-hirokimry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/ship
Command: npx skills add https://github.com/hirokimry/vibecorp --skill ship-hirokimry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual coordination required to take a GitHub Issue from intake to a merged pull request, so Claude Code teams can deliver changes with far less back-and-forth.

Core Features & Use Cases

  • End-to-end issue delivery: Creates the branch, drives planning, implements the work, opens the PR, and prepares auto-merge.
  • Workflow orchestration: Delegates planning, commit creation, PR creation, and review-fix loops to specialized subskills for cleaner responsibility boundaries.
  • Safe operational control: Handles base-branch resolution, worktree mode, intervention points, and post-merge validation for production-style automation.
  • Use case: A developer provides a GitHub Issue URL and wants the repository updated, reviewed, and ready to merge without manually managing each step.

Quick Start

Tell the skill to ship a specific GitHub Issue URL, and it will carry the work from branch creation through PR setup and auto-merge preparation.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a GitHub issue to merged pull request workflow?

To automate a GitHub issue to merged pull request workflow, you can use an orchestration skill that handles branch creation, implementation, PR creation, and auto-merge setup end-to-end. It delegates planning and commits to specialized subskills for safe, deterministic delivery.

What is the best way to ship regular GitHub issues with automated branch management?

Shipping regular GitHub issues with automated branch management is best handled by an orchestration skill that resolves the base branch, drives worktree-aware execution, and sets up intervention checkpoints to ensure safe, automated delivery from issue intake to PR merge.

Do I need GitHub CLI access to automate pull request creation and auto-merge?

Yes, you need GitHub CLI access to automate pull request creation and auto-merge. The workflow relies on the GitHub CLI to interact with the repository, resolve base branches, and prepare pull requests for auto-merge during the automated delivery process.

Can I use workflow automation to handle sub-issues and pull requests in Claude Code repositories?

Yes, you can use workflow automation to handle sub-issues and pull requests in Claude Code repositories. The automation orchestrates the full issue-to-PR shipping workflow, including branch creation, implementation, and review-fix loops, specifically designed for Claude Code environments.

Why does automated PR workflow require intervention checkpoints and guarded retries?

Automated PR workflow requires intervention checkpoints and guarded retries to preserve deterministic and safe automation. These mechanisms allow you to review changes at critical stages and prevent uncontrolled errors during branch creation, implementation, and pull request setup.