gsd-ship

Create pull requests for completed GSD phases with pre-flight checks.

Updated May 11, 2025
One-click install
npx skills add https://github.com/rogsme/dotfiles --skill gsd-ship-rogsme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/rogsme/dotfiles/tree/main/.config/gsd/skills/gsd-ship
Command: npx skills add https://github.com/rogsme/dotfiles --skill gsd-ship-rogsme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of creating a pull request for completed GSD phases, reducing manual effort and ensuring consistency in PR creation.

Core Features & Use Cases

  • Automated PR Creation: Automatically opens a pull request for a completed phase based on verbal commands or specific triggers.
  • Pre-flight Checks: Performs hard preflight checks to ensure all conditions are met before creating the PR, such as verification passed, security gate cleared, clean working tree, and proper branch management.
  • PR Body Generation: Generates a rich PR body with details from the phase's planning artifacts, including summaries, REQ-IDs, verification results, and key decisions.
  • Use Case: After verifying a phase, simply say "/gsd-ship N" to automatically create a PR for phase N, complete with all necessary information.

Quick Start

Use the gsd-ship skill by saying "/gsd-ship N", where N is the phase number you want to ship.

Frequently Asked Questions about gsd-ship

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

FAQPage Schema
How do I automate pull request creation for completed project phases in GitHub?

You can automate pull request creation by using a phase management tool that triggers via commands to generate PRs for completed phases. This specific Skill performs pre-flight checks, generates PR bodies from planning artifacts, and uses GitHub Actions to open PRs automatically.

What pre-flight checks are required before automating a pull request?

Required pre-flight checks for automated pull requests include ensuring verification passed, security gates cleared, a clean working tree, and proper branch management. These hard checks guarantee all conditions are met before the PR is generated.

Can I generate a pull request body from planning artifacts automatically?

Yes, you can generate a rich pull request body directly from planning artifacts. The automated PR creation process extracts summaries, REQ-IDs, verification results, and key decisions from the phase artifacts to populate the PR body.

Does automated PR creation work with the gh command line tool?

Yes, automated PR creation requires the gh command line tool as a dependency. It integrates with GitHub Actions and the gh tool to perform checks and open pull requests for completed project phases.

How do I trigger an automated pull request for a specific phase?

To trigger an automated pull request for a specific phase, you use the command "/gsd-ship N", where N represents the phase number you want to ship. This command initiates the pre-flight checks and PR generation.

What is the best way to manage pull requests for phase-based development?

The best way to manage pull requests for phase-based development is to automate PR creation upon phase completion. This ensures consistency, reduces manual effort, and automatically includes verification results and planning details in the PR body.