gsd-ship

Automates pushing a verified branch, creating a PR with auto-generated body, and tracking merge status.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-ship-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-ship
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-ship-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridge local completion → merged PR. After /gsd-verify-work passes, ship the work: push branch, create PR with auto-generated body, optionally trigger review, and track the merge.

Core Features & Use Cases

  • Automates pushing a feature branch after verification passes and generating an actionable PR description.
  • Creates a PR with an auto-generated body and optional review trigger to accelerate approvals.
  • Tracks merge status from verification completion through to merged PR, ensuring end-to-end visibility.

Quick Start

Trigger the ship workflow after verification passes to push the branch, create a PR with an auto-generated body, and monitor the merge status.

Frequently Asked Questions about gsd-ship

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

FAQPage Schema
How do I automate creating a pull request after local verification passes?

Automate creating a pull request by triggering the ship workflow after verification passes to push a feature branch and generate an actionable PR description automatically. It tracks merge status from verification completion through to the merged PR.

What's the best way to push a git branch and generate a PR body automatically?

Generate a PR body automatically by running the predefined ship workflow, which uses local git commands to push branches and auto-generate actionable PR content. This accelerates approvals by providing an actionable description immediately.

Can I track merge status from verification completion through to a merged PR?

Track merge status by running the ship workflow, which monitors the process from verification completion through to the merged PR. This ensures end-to-end visibility across the entire pull request lifecycle.

Does the ship workflow support triggering optional reviews when creating a PR?

The ship workflow supports optional review triggers when creating a PR with an auto-generated body. This accelerates approvals by optionally notifying reviewers after the feature branch is pushed and the PR is created.

When do I need to run the end-to-end ship flow after CI-CD verification?

Run the end-to-end ship flow after CI-CD verification passes to bridge local completion to a merged PR. It handles pushing the verified branch, creating the PR, and monitoring the merge status automatically.