gsd-ship

Create a merge-ready pull request after verification passes in GitHub workflows.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-ship-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-ship
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-ship-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the coordination gap between local completion and a fully verified, merge-ready pull request.

Core Features & Use Cases

  • Verify-gated shipping loop: Bridges your work from local completion to shipping only after verification passes, closing the loop from plan → execute → verify → ship.
  • PR creation with automation: Pushes the branch and generates a PR body automatically to reduce manual PR preparation.
  • Optional review triggering: Supports running the review step when needed and helps track the merge outcome.

Quick Start

Run the gsd-ship flow that executes the ship workflow from .github/get-shit-done/workflows/ship.md end-to-end after your verification phase completes.

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 only after verification passes?

Verify-gated shipping automates pull request creation by pushing your local branch and generating a PR body only after verification passes, closing the loop from local completion to a merge-ready state.

What is verification gating in a GitHub release workflow?

Verification gating in a GitHub release workflow ensures local code changes are not pushed to a pull request until verification checks pass, bridging local completion to a merge-ready state.

How do I run the ship workflow end-to-end from my repository?

Run the gsd-ship flow to execute the ship workflow from .github/get-shit-done/workflows/ship.md, completing the push, PR creation, review, and merge tracking loop end-to-end.

Does merge automation support optional review tracking for GitHub pull requests?

Yes, the shipping loop supports running an optional review step when needed and tracks the merge outcome, ensuring the GitHub PR review and merge process is monitored end-to-end.

What is the best way to generate a PR body automatically from local changes?

Using verify-gated shipping automation is an effective way to generate a PR body automatically, pushing your branch and creating the PR body to reduce manual preparation after verification completes.