ship-issue

Drive Linear issues from Backlog to Done with PR/MR creation and merging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual, error-prone work of driving a Linear ticket through implementation, PR/MR creation, review response, and merge completion—especially when changes span GitHub and GitLab repos.

Core Features & Use Cases

  • End-to-end implement → PR → review → merge loop: Selects the next non-terminal ticket item and advances it through the required lifecycle steps.
  • Cross-platform support (GitHub + GitLab): Detects the hosting platform from the repo’s origin and uses the right CLI to open and monitor PRs/MRs.
  • Multi-repo parent workflows: Resolves sub-issues via repo:<name> labels, runs them serially in Linear order, and handles repo/label ambiguity safely.
  • Safety guardrails and idempotent resumption: Polls on a fixed cadence, resumes from derived state using Linear + host truth, and halts on blocked or failed conditions rather than silently continuing.

Quick Start

Invoke /ship-issue PROJ-88 and let the workflow open the PR/MR, handle review feedback, and merge when ready.

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 Linear issue from backlog to merge across multiple repos?

You can automate a Linear issue from backlog to merge by invoking a workflow that implements the work, opens a platform-correct PR or MR, addresses review feedback, and merges. It handles parent issues with sub-issues across multiple repos.

Can I use GitHub and GitLab CLI tools to automate code shipping for Linear tickets?

Yes, you can automate code shipping using Linear MCP access along with platform CLIs like gh or glab. The workflow detects the hosting platform from the repo origin and uses the correct CLI to open and monitor PRs or MRs automatically.

What is the best way to handle review feedback and merge PRs automatically?

The best way to handle review feedback and merge PRs automatically is using a workflow that polls on a fixed cadence, responds to review comments, and merges when ready. It resumes from derived state using Linear and host truth to ensure idempotent correctness.

Does workflow orchestration for code shipping support milestone-wide ordering?

Yes, workflow orchestration for code shipping supports milestone-wide ordering using createdAt ordering. It selects the next non-terminal ticket item and advances it through the required lifecycle steps, handling single tickets, ordered lists, and parent issues with sub-issues.

What happens when a PR merge fails or a user is blocked during review automation?

When a PR merge fails or a user is blocked during review automation, the workflow halts on blocked or failed terminal conditions rather than silently continuing. It enforces stateless correctness via derive-and-resume logic with built-in guardrails to prevent unsafe operations.