skills.rest
electroheadfx
electroheadfxCOMMUNITY
Explore all skills by this author →
GitHub

gsd-ship

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

4|Updated Apr 11, 2026
Search Tags:#workflow#pull request#shipping#merge#review#branch
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-ship-electroheadfx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-ship
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-ship-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you move completed work from local verification to a merge-ready pull request without losing track of the release process.

Core Features & Use Cases

  • Branch shipping: Push the current branch and prepare it for delivery.
  • Pull request creation: Generate a PR with an auto-written body based on the completed work.
  • Review and merge coordination: Optionally trigger review, track merge readiness, and follow the end-to-end ship workflow.
  • Use Case: After validation passes on a feature branch, use this Skill to package the changes into a PR and guide the final path to merge.

Quick Start

Ask the skill to ship the verified branch and create the pull request for the completed changes.

Frequently Asked Questions about gsd-ship

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

FAQPage Schema
How do I move verified local branch changes into a merge-ready pull request?▼

To move verified local branch changes into a merge-ready pull request, this Skill pushes the current branch and generates a PR with an auto-written body based on the completed work.

What is the best way to coordinate review and merge readiness after pushing a branch?▼

The best way to coordinate review and merge readiness is using a shipping workflow that tracks the branch-to-PR state, optionally triggers review, and guides the final path to merge.

How does the branch-to-PR shipping workflow track release state?▼

The branch-to-PR shipping workflow tracks release state by coordinating branch operations, PR generation, and review coordination to complete the ship process safely.

Can I generate a pull request body automatically from my completed branch work?▼

Yes, you can generate a pull request body automatically from completed branch work; the Skill creates a PR with an auto-written body documenting the verified changes for review.

When should I use an automated shipping workflow for pull request creation?▼

You should use an automated shipping workflow for pull request creation after validation passes on a feature branch and you need to package changes and prepare for merge.

Does the shipping workflow handle the entire path from branch push to merge?▼

Yes, the shipping workflow handles the entire path from branch push to merge by moving completed work into a merge-ready pull request and tracking the end-to-end delivery process.

Related Skills

Explore More Software Engineering Skills→
rkz91rkz91
264

gsd-ship

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

Community
Advanced
coco-researchcoco-research
264

gsd-ship

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

Community
Advanced
lilmuckerslilmuckers

branch-pr-lifecycle

Coordinate feature-branch workflows and draft pull requests for review.

Community
Intermediate
alistairhendersoninfoalistairhendersoninfo

ship-it

Automate Git workflows from branch creation to pull request merge.

Community
Advanced