ship-it

Orchestrate GitHub issue creation, planned implementation, PR opening, and release workflows.

3|1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Garsdal/Dojo --skill ship-it-garsdal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-it
Source: https://github.com/Garsdal/Dojo/tree/main/.claude/skills/ship-it
Command: npx skills add https://github.com/Garsdal/Dojo --skill ship-it-garsdal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end “prompt → shipped/released” workflow so users can move from a change request to a merged pull request and published release with clear human checkpoints.

Core Features & Use Cases

  • Issue creation from intent: Converts a short request into a GitHub issue via the create-issue phase.
  • Two-phase solution with review gates: Generates and writes an implementation plan, pauses for user plan review, then implements and opens a PR.
  • Post-merge verification and optional publishing: Verifies linked issues are actually closed, then—only when release instructions exist and the user signals—tags and triggers the publish flow.
  • Use case: When you want a whole loop from “ship this change” to a merged PR and a release, without manually coordinating issue creation, planning, implementation, and release steps.

Quick Start

Tell the AI “ship-it: <describe the change>” and then review the generated plan and prompt “continue” to implement and open a PR.

Frequently Asked Questions about ship-it

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

FAQPage Schema
How do I automate the full GitHub workflow from issue creation to release?

Automating the full GitHub release workflow involves orchestrating issue creation, implementation planning, PR opening, and post-merge version tagging. This Skill coordinates the entire loop with explicit human review gates between the planning and implementation phases.

Can I add human review gates between planning and opening a pull request?

Yes, human review gates are built into the workflow orchestration. The Skill generates an implementation plan, pauses for your explicit review and approval, and only then implements the changes and opens a pull request.

Does release automation verify linked GitHub issues are closed before version tagging?

Release automation verifies PR merge state and linked issue closure before proceeding. Version tagging and the publish flow are only triggered when release conditions are satisfied and you explicitly signal to continue.

What is the best way to turn a short prompt into a merged pull request and published release?

The best way to turn a short prompt into a published release is triggering an end-to-end change delivery loop. The Skill converts your request into a GitHub issue, plans the implementation, opens a PR, and tags a release after merge.

Do I need separate tools for issue creation and version tagging in my release workflow?

You do not need separate tools for issue creation and version tagging if you use a unified workflow orchestration approach. This Skill manages both phases, coordinating solve-issue and create-issue steps within a single automated pipeline.

When should I not use an end-to-end release automation workflow?

You should not use end-to-end release automation when you only need a single step like writing code or opening a PR. This approach is designed for the complete create, plan, review, PR, and release loop rather than isolated tasks.