gsd-ship

Create a pull request and shipping plan after verification passes.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-ship-deerawan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-ship
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-ship-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction between having verified work locally and getting it merged through a clean, reviewable pull request.

Core Features & Use Cases

  • End-to-end ship workflow: Executes the ship process end-to-end as defined by the repo’s ship workflow so the work advances toward merge.
  • Verify-then-ship loop: Bridges completion to merging by following the plan → execute → verify → ship cycle, ensuring shipping happens after verification passes.
  • PR creation for collaboration: Pushes the branch, creates a PR with an auto-generated body, and can trigger review while tracking the merge.

Quick Start

Run the gsd-ship workflow end-to-end using the ship workflow instructions located at ~/.claude/get-shit-done/workflows/ship.md.

Frequently Asked Questions about gsd-ship

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

FAQPage Schema
How do I automate pull request creation after local code verification passes?▼

Automating pull request creation after verification passes requires running a ship workflow that bridges completed work to a merged GitHub change by pushing the branch and auto-generating the PR body. This ensures PR creation only happens after verification passes.

What is a verify-then-ship workflow for milestone-driven development?▼

A verify-then-ship workflow follows the plan, execute, verify, and ship cycle to gate branching, PR creation, review triggering, and merge tracking across milestones. It ensures shipping proceeds only after local code verification passes.

How do I trigger a code review and track merge status for a pull request?▼

Triggering a code review and tracking merge status involves pushing a branch and creating a PR with an auto-generated body that triggers review while tracking the merge. This Skill handles these steps within its end-to-end ship workflow.

Does this workflow automation require any specific dependencies to run?▼

This workflow automation requires no external dependencies to run. It executes the ship process using workflow instructions located at the specified path, handling push, PR creation, review, and merge tracking natively.

Can I use this ship workflow for tracking merges across multiple development milestones?▼

Yes, you can use this ship workflow for tracking merges across multiple development milestones. It applies to workflow-driven development scenarios where verification status gates branching, review triggering, and merge tracking across phases.

Why should I use a verify-then-ship loop instead of manually creating pull requests?▼

Using a verify-then-ship loop removes the friction between having verified work locally and getting it merged through a clean, reviewable pull request. It ensures merge readiness by gating PR creation behind successful verification.