gsd-ship

Push verified branches and open pull requests for merge tracking.

Updated May 22, 2026
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-ship-yusaduymaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-ship
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-ship-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill closes the gap between verified local work and a shipped pull request, handling the final steps that turn completed changes into a mergeable delivery.

Core Features & Use Cases

  • Pushes the current branch after verification passes.
  • Creates a pull request with an autogenerated body and can trigger review.
  • Tracks merge progress so you know when the work is fully shipped.
  • Useful for release-ready feature branches, hotfixes, and collaborative code review handoffs.

Quick Start

Use the gsd-ship skill to push the verified branch, open a pull request, and continue tracking it until merge.

Frequently Asked Questions about gsd-ship

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

FAQPage Schema
How do I push a verified git branch and create a pull request automatically?

It handles the final shipping steps by pushing the verified git branch and opening a GitHub pull request with an autogenerated body for merge tracking. This bridges the gap between local verification and a mergeable delivery.

How do I track GitHub pull request merge status after pushing a release-ready branch?

You can track GitHub pull request merge status by using this skill to monitor the merge progress after opening the PR. It ensures you know exactly when your release-ready feature branch or hotfix is fully shipped.

Can I trigger a code review when opening a GitHub pull request?

Yes, you can trigger a code review when opening a GitHub pull request. The skill orchestrates review creation alongside the autogenerated PR body, supporting collaborative code review handoffs for release-ready workflows.

Do I need local verification to pass before pushing my branch and opening a pull request?

Yes, local verification must pass before pushing your branch and opening a pull request. This skill is designed for release-ready development workflows that require verified work before initiating GitHub PR creation and merge monitoring.

What is the best way to automate git branch delivery for collaborative code review handoffs?

The best way to automate git branch delivery is to push the verified branch and open a pull request with an autogenerated body. This enables seamless collaborative code review handoffs and tracks merge progress until completion.