ship-issue-gh

Drive GitHub issues through implementation, PR review, and merge.

Updated May 20, 2026
One-click install
npx skills add https://github.com/semanticpixel/abc --skill ship-issue-gh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-issue-gh
Source: https://github.com/semanticpixel/abc/tree/main/plugins/abc/skills/ship-issue-gh
Command: npx skills add https://github.com/semanticpixel/abc --skill ship-issue-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ship-issue-gh eliminates the manual coordination work of taking a GitHub issue (including parent issues with managed sub-issues) through implementation, PR creation, review handling, and eventual merge by continuously resuming from GitHub’s current state.

Core Features & Use Cases

  • GitHub-only end-to-end issue driving loop: moves a target issue through implementing → PR open → review/fix loop → merged while treating GitHub Issues and PR check runs as the sources of truth.
  • Ordered queues and parent task-list support: accepts a single issue, an ordered comma-separated list, a parent issue whose body contains a managed Sub-issues task-list, or milestone-based expansion, then processes items in the specified order.
  • Deterministic self-arming and safe guardrails: self-arms its own loop at a fixed cadence, derives state from labels/PR activity without local persistence, and hard-stops on “self-cheating” or unrecoverable correctness failures.

Quick Start

In your repo (with GitHub access configured), tell Claude Code to run: /ship-issue-gh owner/repo#42.

Frequently Asked Questions about ship-issue-gh

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

FAQPage Schema
How do I automate GitHub issues from implementation through PR merge?

Automating GitHub issues from implementation to merge requires driving the issue state continuously based on PR activity. This involves moving a target issue through implementing, PR open, review fixing, and merged states while treating GitHub Issues and PR check runs as sources of truth.

Can I process a parent GitHub issue with a managed sub-issues task list?

Processing a parent GitHub issue with a managed sub-issues task list is supported. The system discovers child issues from a managed Sub-issues block in the parent issue body and processes items in the specified order, alongside support for ordered comma-separated lists and milestone expansions.

How do GitHub PR review comments and CI check runs factor into issue automation?

GitHub PR review comments and CI check runs serve as the operational sources of truth for issue automation. The workflow derives state from labels and PR activity without local persistence, using these signals to drive the issue from pending through implementation to a merged terminal state.

Does this GitHub issue workflow handle multiple repositories in an ordered queue?

Handling multiple repositories in an ordered queue is supported. You can provide an ordered comma-separated list across repositories, and the system will process items in the specified order, expanding milestones or parent issue task lists as needed.

What safety guardrails exist for automating GitHub issue state transitions?

Safety guardrails for automating GitHub issue state transitions include locked state transitions and hard-stop rules. The system enforces safety by hard-stopping on unrecoverable correctness failures or self-cheating scenarios, using deterministic self-arming and idempotent loops.