gsd-ship

Push a branch, create a PR with an auto-generated body, and track merge status.

8|Updated Apr 9, 2026

Search Tags:#automation #workflow #verification #merge #ship #pull-request

Ready to run

npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-ship-d0nmega

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-ship
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-ship-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges the final gap between local completion and merged code by automating PR creation, review triggering, and merge tracking after verification passes.

Core Features & Use Cases

End-to-end ship workflow: push branch, auto-generate PR body, optionally start a review, and monitor merge status.
Verification-first release: ensures changes only ship after successful /gsd-verify-work validation.
AI-assisted PR polish: creates a clean PR description and structured summary for reviewers.

Quick Start

Run the ship workflow after verification to push the branch, generate an auto-generated PR, and begin merge tracking.

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 and merge tracking after local code verification?▼

Automating pull request creation and merge tracking involves running an end-to-end ship workflow that pushes your branch, generates a PR body, optionally starts a review, and monitors merge status using standard Git tooling.

What is an end-to-end ship workflow for verified code changes?▼

An end-to-end ship workflow bridges local completion and merged code by pushing branches, auto-generating PR descriptions, optionally triggering reviews, and tracking merge status after validation passes.

Do I need to run code verification before automating a pull request?▼

Yes, code verification is required first. The ship workflow is verification-first, ensuring changes only push and create a pull request after successful validation prevents unverified code from merging.

How do I generate a structured pull request description for reviewers automatically?▼

You can generate a structured pull request description by using an AI-assisted ship workflow that auto-generates a clean PR body and summary from your verified local code changes for reviewers.

Can I trigger code reviews automatically when pushing a branch?▼

Yes, you can trigger code reviews automatically. The ship workflow optionally starts a review process immediately after creating the pull request with an auto-generated body from your verified changes.

What is the best way to track merge status after creating a pull request?▼

The best way to track merge status is using an automated ship workflow that monitors the merge state continuously after pushing the branch, generating the PR, and optionally triggering reviews.