gsd-ship

Create a merge-ready pull request from verified GSD workflow work.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-ship-beibei-clic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/BeiBei-Clic/ai-skills/tree/main/gsd-ship
Command: npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-ship-beibei-clic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning locally completed work into a reviewed, verifiable, and merged pull request is often delayed by manual steps and unclear coordination between planning, verification, review, and release.

Core Features & Use Cases

  • Creates a merge-ready PR from verified work: Pushes the branch, generates a PR description body automatically, and ensures the workflow continues after verification succeeds.
  • Optionally triggers review: Can initiate review steps when appropriate to accelerate feedback before merging.
  • Tracks the plan → execute → verify → ship loop: Keeps the workflow aligned with the intended phase or milestone so teams can follow progress end-to-end.

Example use case: after completing a planned feature and ensuring /gsd:verify-work passes for phase 4, use gsd-ship to open the PR and move the work toward merging without redoing setup and documentation work.

Quick Start

Run gsd-ship for phase 4 after your verification step succeeds to automatically create a PR and prepare it for merge.

Frequently Asked Questions about gsd-ship

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

FAQPage Schema
How do I create a pull request from a verified Git branch and track it for merge?▼

gsd-ship creates a merge-ready pull request by pushing your local branch, generating a PR description body automatically, and tracking the merge workflow to keep phase or milestone progress aligned.

What is the best way to automate PR creation after local verification passes?▼

Automating PR creation after verification passes is handled by running gsd-ship, which moves work from execution into PR-based integration by pushing the branch and opening the pull request without manual setup.

How does the plan to execute verify ship loop work with Git merge tracking?▼

The plan, execute, verify, ship loop works by coordinating local completion with Git PR creation, ensuring work moves into PR-based integration only after verification succeeds, while tracking progress against milestones.

Can I trigger code review automatically when opening a pull request?▼

Yes, gsd-ship optionally triggers code review steps when opening a pull request to accelerate feedback before preparing the branch for merge.

Does gsd-ship require a specific CI readiness check before preparing for merge?▼

gsd-ship requires verification to pass before preparing for merge, aligning with CI readiness by ensuring the end-to-end ship process runs only after local completion and verification succeed.

When should I not use an automated PR workflow for Git branching?▼

You should not use an automated PR workflow for Git branching if your local work has not passed the verification step, as gsd-ship requires the plan, execute, verify loop to complete before PR creation.