gh-ship

Open a GitHub PR from the current feature branch and manage CI, merge, and post-merge verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RonanCodes/ronan-skills --skill gh-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-ship
Source: https://github.com/RonanCodes/ronan-skills/tree/main/skills/gh-ship
Command: npx skills add https://github.com/RonanCodes/ronan-skills --skill gh-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drive an end-to-end GitHub feature ship workflow, opening PRs, watching CI, merging, and validating post-merge deployment.

Core Features & Use Cases

  • Open a PR from the current feature branch and monitor CI checks until merge readiness.
  • Support multiple merge strategies (--squash / --merge / --rebase) and post-merge verification.
  • Use case: ship a new feature from a feature branch to production, with optional auto-deploy scaffolding.

Quick Start

Open a PR from the current feature branch and begin the full GitHub ship workflow.

Frequently Asked Questions about gh-ship

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

FAQPage Schema
How do I automate GitHub PR creation and CI monitoring from a feature branch?

Automating GitHub PR creation and CI monitoring involves opening a pull request from your current feature branch and watching checks until merge readiness. This workflow handles PR title and body derivation, continuous integration check watching, and merge decisions.

What is the best way to manage GitHub merge strategies and post-merge deployment?

Managing GitHub merge strategies and post-merge deployment requires applying squash, merge, or rebase options followed by deployment validation. The process includes post-merge pipelines and optional auto-deploy scaffolding to validate production changes.

Can I ship a feature branch to production with end-to-end GitHub workflow automation?

Shipping a feature branch to production with end-to-end GitHub workflow automation supports standard feature-branch workflows. It implements sanity checks, PR creation, CI check watching, merge decisions, and post-merge pipeline validation to ensure successful deployment.

Does GitHub CI check watching support multiple merge options for pull requests?

GitHub CI check watching supports multiple merge options for pull requests including squash, merge, and rebase strategies. The workflow monitors continuous integration checks until merge readiness is achieved, then executes the selected merge decision and post-merge verification.

How do I validate post-merge deployment pipelines after a GitHub PR merge?

Validating post-merge deployment pipelines after a GitHub PR merge involves running post-merge verification and deployment validation steps. The workflow executes post-merge pipelines and optional auto-deploy scaffolding to confirm production deployment success.