ship-issue

Resolve small GitHub issues end to end through merged pull requests.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill ship-issue-gittower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-issue
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/ship-issue
Command: npx skills add https://github.com/gittower/git-flow-next --skill ship-issue-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill takes a small, well-scoped GitHub issue all the way from implementation to merged pull request, reducing the manual coordination needed to resolve, review, and ship a fix.

Core Features & Use Cases

  • End-to-end issue delivery: Resolves the issue, publishes the branch, opens the PR, and manages the merge path.
  • Automated review handling: Runs two rounds of Copilot review, applies accepted fixes, and resolves review threads.
  • Safety-first escalation: Stops and asks for help when the issue is ambiguous, a review finding is uncertain, conflicts are non-trivial, or CI/build status is not healthy.
  • Use case: Use this when you want an AI to autonomously handle a small bug fix or documentation-plus-code change from issue number to merged PR with minimal oversight.

Quick Start

Ask the assistant to ship issue number 123 end-to-end, with no merge if you want to review the final state yourself.

Frequently Asked Questions about ship-issue

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

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

To automate a GitHub issue end to end, this Skill implements the fix, publishes a branch, opens a pull request, runs Copilot reviews, validates builds, and manages the merge path autonomously with explicit escalation points.

What is the best way to handle Copilot review findings on a pull request autonomously?

Handling Copilot review findings involves running two review rounds, applying accepted fixes automatically, and resolving review threads. The process stops and escalates only when a review finding is uncertain or conflicts are non-trivial.

Can I use Git worktrees to resolve small bug fixes and documentation-plus-code tasks?

Yes, Git worktrees are required to resolve small bug fixes, flag changes, and documentation-plus-code tasks. This Skill uses them to isolate tightly scoped changes for autonomous delivery from issue resolution through merge readiness.

When should I not use autonomous merge automation for a GitHub pull request?

You should not use autonomous merge automation when the GitHub issue is ambiguous, review findings are uncertain, conflicts are non-trivial, or the CI/build status is not healthy. The Skill stops and asks for help in these specific scenarios.

Does this GitHub workflow integrate build and test validation before attempting a merge?

Yes, build and test validation is integrated directly into the workflow. The process runs safety checks, validates build and test status, and pauses the merge if the CI or build health is not confirmed before proceeding.

How do I ship a small fix from issue to merge with no automatic merge?

To ship a small fix without an automatic merge, ask the assistant to ship the issue end to end with no merge. The Skill will implement the fix, publish the branch, open the PR, and manage reviews, leaving the final merge to you.