gsd-ship

Push a verified branch and create a GitHub PR with an auto-generated body.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-ship-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-ship
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-ship-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of getting work shipped reliably by bridging the gap between completing local changes and having them merged through a PR with verification.

Core Features & Use Cases

  • PR creation and merge readiness: Pushes the prepared branch and creates a PR with an auto-generated body so reviewers have context.
  • Optional review triggering: Can initiate a review step when you want additional verification before merging.
  • Merge tracking and loop closure: Tracks progress until the merge completes, closing the plan → execute → verify → ship loop.

Quick Start

Run the ship workflow end-to-end to create a PR and merge it after verification passes: openforce /gsd:ship 4

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

To automate pull request creation and merge after local verification passes, this Skill pushes a prepared git branch and creates a GitHub PR with an auto-generated body. It tracks merge completion to close the plan, execute, verify, and ship workflow loop.

What is the best way to trigger a code review before merging a verified git branch?

The best way to trigger a code review before merging a verified git branch is using the optional review triggering feature. It initiates a review step after the auto-generated PR body is created, providing additional verification before final merge completion.

Does the merge workflow require a verification gate to run successfully?

Yes, the merge workflow requires a verification gate to run successfully. The ship workflow must execute after the /gsd:verify-work command passes, ensuring locally completed work is bridged into a merged GitHub PR only when verification succeeds.

How do I generate a PR body automatically when pushing a branch for code review?

To generate a PR body automatically when pushing a branch for code review, execute the ship workflow. It pushes the prepared branch and creates an auto-generated PR body, giving reviewers the necessary context for the repository update.

Can I use this merge workflow to track pull request progress until completion?

Yes, you can use this merge workflow to track pull request progress until completion. It tracks progress throughout the repository ops process, ensuring the merge completes and closing the plan execution, verification gating, and shipping loop.