skills.rest
tinner-deinno
tinner-deinnoCOMMUNITY
Explore all skills by this author →
GitHub

gsd-ship

Creates a merge-ready pull request from locally verified work and tracks its merge.

1|Updated May 24, 2026
Search Tags:#code review#pull request#merge#git workflows#CI verification#gsd#release milestone
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-ship-tinner-deinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-ship
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-ship-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the gap between successful verification and getting changes merged, so work doesn’t stall after /gsd:verify-work completes.

Core Features & Use Cases

  • Automated merge-readiness shipping: Pushes the branch, creates a PR with an auto-generated body, and tracks the merge after verification passes.
  • Optional review triggering: Initiates review when desired to keep the feedback loop moving.
  • Use Case: After completing a verified milestone (e.g., v1.0 or phase 4), use this Skill to convert that verified work into a ready-to-merge PR and close the plan → execute → verify → ship loop.

Quick Start

Run the gsd-ship workflow with the argument "4" to ship the verified changes from that phase into a merged PR.

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 merge-ready pull request after local verification passes?▼

To create a merge-ready pull request after verification, use an automated ship workflow that pushes your branch and generates the PR body. This tracks the merge status to bridge the gap between local completion and repository integration.

What is the best way to automate PR creation from verified git workflows?▼

Automating PR creation from verified git workflows involves executing an end-to-end ship process that pushes the branch and creates a pull request with an auto-generated body. This ensures changes are merge-ready immediately after verification gates pass.

Do I need to run a verification gate before shipping a release milestone?▼

Yes, running a verification gate such as /gsd:verify-work before shipping a release milestone is required. The ship workflow converts locally verified work into a pull request, ensuring only validated changes are pushed for repository integration.

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

Yes, you can trigger a code review automatically when creating a pull request. The ship workflow includes optional review triggering functionality to initiate the review process and keep the feedback loop moving after PR creation.

How does merge tracking work for pull requests in CI verification workflows?▼

Merge tracking in CI verification workflows monitors the pull request status after creation to ensure verified changes are successfully merged. This completes the plan, execute, verify, and ship loop by tracking repository integration.

What are the limitations of automating pull request creation from verified work?▼

Limitations of automating pull request creation include its dependency on specific software delivery workflows following verification gates. It requires executing the end-to-end ship workflow from a specified path and completing PR creation and merge tracking requirements.

Related Skills

Explore More Software Engineering Skills→
dmulcaheydmulcahey

verification-before-completion

Require verifiable evidence before marking work complete in code reviews.

Community
Intermediate
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
diShine-digital-agencydiShine-digital-agency
1

shine-autonomous

Automate remaining milestone phases through discuss, plan, and execute cycles.

Community
Advanced
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic