ship-pr

Trigger auto-approve on a GitHub PR, merge on approval, and verify post-merge deployment health.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a pull request safely requires confirming every review thread is answered, CI is green, the branch is current, and the deployment stays healthy afterward. Doing this by hand across GitHub comments, reviews, workflow runs, and cluster health checks is slow and error-prone. ## Core Features & Use Cases - Hard pre-merge gates: Blocks the merge until prior review exists, all review threads are resolved, no active CHANGES_REQUESTED reviews remain, reviewer questions are answered, and CI on the head commit passes. - Auto-approve workflow orchestration: Posts the @auto-approve comment, waits for the GitHub Actions run, reads the APPROVE or REQUEST_CHANGES verdict, and merges only on approval. - Post-merge cleanup and verification: Resets to the default branch, deletes merged branches, waits for the merge commit's CI runs, and probes deployment health on Kubernetes, VM, PaaS, or serverless platforms. - Use Case: After hero-skills:review-pr marks your PR ready and bot reviews finish, run this skill to gate, merge, clean up branches, and confirm the deploy is healthy in one pass. ## Quick Start Ask the assistant to ship the current pull request with the ship-pr skill after review is complete.

Frequently Asked Questions about ship-pr

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

FAQPage Schema
How do I automatically merge a GitHub PR after approval?

Post an @auto-approve comment that triggers an issue_comment GitHub Actions workflow, wait for the run's verdict, and merge on APPROVE. The skill gates this on resolved threads, green CI, and no active CHANGES_REQUESTED reviews before posting the trigger.

How to check unresolved review threads on a GitHub PR with gh CLI?

Use gh api graphql with the reviewThreads field to list threads where isResolved is false and isOutdated is false. The skill counts these and refuses to merge until every inline conversation is resolved.

Why is my issue_comment workflow not triggering on GitHub?

GitHub only honors issue_comment workflows that already exist on the default branch, so the workflow file must be merged to main first. On public repos the job may also be gated on the repository being private, causing the run to be skipped.

Does this work with bot-authored PRs like Dependabot?

Yes, but the unanswered-questions gate is skipped for bot authors because bots never post top-level comments, which would otherwise make every human comment score as permanently unanswered. The skip is reported explicitly rather than shown as a clean pass.

What happens if CI is still pending when I try to merge?

The skill polls gh pr checks locally for up to 30 minutes, treating empty output as registration lag for the first two minutes. If checks remain pending after the deadline, it stops and refuses to post the auto-approve trigger into a pending build.

Can it verify deployment health after merging?

Yes, after merge it waits up to ten minutes for the merge commit's workflow runs, then probes deployment health per the platform declared in HERO.md: Kubernetes via kubectl or argocd, or VM and PaaS via curl-reachable health endpoints. Results are advisory only.