skills.rest
jjchambers80
jjchambers80COMMUNITY
Explore all skills by this author →
GitHub

gsd-ship

Creates pull requests, runs review, and prepares merges after verification passes.

Updated Feb 18, 2026
Search Tags:#git#code review#pull request#workflow automation#github#merge#ship
One-click install
npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-ship-jjchambers80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/jjchambers80/judgesdirectory/tree/main/.github/skills/gsd-ship
Command: npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-ship-jjchambers80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After implementation work is verified, developers still face the manual overhead of pushing branches, writing PR descriptions, triggering reviews, and tracking merges. This Skill automates that final shipping step so verified work reaches a merged PR without repetitive manual effort. ## Core Features & Use Cases - Automated PR Creation: Pushes the working branch and generates a pull request with an auto-generated body summarizing the completed work. - Review Triggering: Optionally kicks off a code review step before merge to maintain quality gates. - Merge Tracking: Monitors the PR through to merge, closing the plan → execute → verify → ship loop. - Use Case: After running verification on phase 4 of a milestone, invoke this Skill to push the branch, open a PR with a generated summary, run review, and track it to merge. ## Quick Start Ship the verified work for phase 4 by creating a pull request and preparing 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 automatically after verification?▼

Invoke the ship workflow with a phase number or milestone argument after verification passes. It pushes the current branch, generates a PR body from the completed work, and opens the pull request on GitHub.

How to auto-generate a pull request description from completed work?▼

The ship workflow builds the PR body automatically from the verified phase or milestone context. You supply the phase number or milestone name, and the generated summary is included when the PR is created.

Can I trigger a code review before merging a pull request?▼

Yes, the ship workflow includes an optional review step that runs after the PR is created. This keeps a quality gate between PR creation and merge without requiring a separate manual process.

What should I run before shipping work to a pull request?▼

Run the verification step first, since the ship workflow is designed to execute only after verification passes. Shipping unverified work bypasses the plan, execute, verify, ship loop the workflow enforces.

Does the ship workflow track the pull request through merge?▼

Yes, merge tracking is part of the workflow. After the PR is created and optionally reviewed, the workflow monitors it through to merge, completing the development loop.

Related Skills

Explore More Software Engineering Skills→
GregoryHoGregoryHo
6

arc-finishing-epic

Finalize epic implementations in a worktree by verifying tests and presenting integration options.

Community
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

land-and-deploy

Merge pull requests, monitor CI, deploy to production, and verify health with canary checks.

Community
Intermediate
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
deepgramdeepgram
23

github

Automate GitHub issues, pull requests, and CI runs via the gh CLI.

Official
Intermediate