skills.rest
Jeqqe
JeqqeCOMMUNITY
Explore all skills by this author →
GitHub

ship

Orchestrate GitHub issues into merged pull requests with bounded fix loops.

Updated Aug 27, 2026
Search Tags:#automation#code review#github#CI checks#issue to pr#branch orchestration#bounded fix loop
One-click install
npx skills add https://github.com/Jeqqe/jersal-project-template --skill ship-jeqqe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Jeqqe/jersal-project-template/tree/main/.pi/skills/ship
Command: npx skills add https://github.com/Jeqqe/jersal-project-template --skill ship-jeqqe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship turns a single GitHub issue into a ready-to-merge pull request by coordinating planning, implementation, review, and a bounded fix loop without duplicating work across phases.

Core Features & Use Cases

  • Single-run issue-to-PR orchestration: Executes the existing phase skills (plan → implement → review → fix loop → debrief → PR) with shared context gathered once.
  • Bounded fix loop with decision gates: Re-runs implementation and review up to three times only for review blockers, and stops to ask when product/architecture decisions are required.
  • Two operating modes for workflow control: Standalone mode creates the PR and closes issues; batch mode (--no-pr) pushes a clean branch without opening a PR and defers debrief writing for later consolidation.
  • Use Case: When a teammate requests an end-to-end fix for a specific issue, use ship to go from issue triage to a high-quality PR in one execution while ensuring clear stop-and-ask checkpoints for risky or ambiguous changes.

Quick Start

Run /skill:ship 123 to take issue 123 from planning through review and (if it passes) open a PR that closes the issue.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate turning a GitHub issue into a pull request?▼

To automate issue-to-PR delivery, you can orchestrate end-to-end phases from planning to implementation and review. This coordinates the entire workflow into a single execution, generating a ready-to-merge pull request that closes the original issue.

What is a bounded fix loop in CI code review automation?▼

A bounded fix loop in code review automation re-runs implementation and review up to three times for blockers. It enforces decision gates and stops to ask for product or architecture decisions instead of guessing when confidence is reduced.

How do I stop automated code review from making risky changes?▼

To stop automated code review from making risky changes, enforce decision gates for NEEDS DECISION items. The orchestration stops instead of guessing when confidence is reduced, requiring explicit input on ambiguous changes.

Can I push a GitHub branch without opening a pull request?▼

Yes, you can push a clean branch without opening a pull request using batch mode. This mode defers debrief writing for later consolidation and skips the PR creation step until you are ready.

What are the limitations of automated branch orchestration for GitHub issues?▼

Limitations of automated branch orchestration include a maximum of three retry rounds for review blockers before escalation. It also requires reading shared agent context once and will halt execution when product or architecture decisions are needed.

Related Skills

Explore More Software Engineering Skills→
darthlinuxerdarthlinuxer

create-pull-request

Create GitHub pull requests from feature branches using the gh CLI.

Community
Advanced
reggiechan74reggiechan74
5

git-workflow

Create safe Git commits and pull requests with the GitHub CLI.

Community
Intermediate
icliniciclinic
9

implementing

Orchestrate subagent-driven development tasks during the implementing phase.

Official
Advanced
hirokimryhirokimry
1

review-loop

Iteratively review, validate, and repair code until findings are resolved.

Community
Advanced