qsd-ship

Push a branch and create a PR with an auto-generated body after verification passes.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/thecomputer07/qsd --skill qsd-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qsd-ship
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-ship
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridge local completion into a merged pull request after verification passes, automating PR creation and merge-tracking to streamline shipping.

Core Features & Use Cases

  • Auto-generate PR bodies and push the branch for merging after a verification workflow completes.
  • Trigger optional reviews and monitor merge status to ensure safe, auditable delivery.
  • Use case: after finishing a phase, run the ship workflow to open a PR, request review if needed, and merge once verification passes.

Quick Start

After verification passes, run the ship workflow to push your branch, create a PR with an auto-generated body, and monitor the merge.

Frequently Asked Questions about qsd-ship

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

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

Automate pull request creation by pushing your branch and generating a PR body automatically once verification passes. This ship workflow bridges local completion to a merged PR by orchestrating review triggering and tracking merge status for safe delivery.

What is automated PR shipping in a phase-driven development workflow?

Automated PR shipping bridges local phase completion to a merged pull request by pushing the branch, auto-generating the PR body, optionally triggering code review, and tracking the merge after verification passes.

How do I trigger a code review automatically when creating a pull request?

Trigger a code review automatically during the ship workflow by enabling the optional review triggering feature. After pushing the branch and creating the PR, the workflow requests a review and monitors the merge status.

Can I track merge status automatically after opening a pull request?

Yes, you can track merge status automatically after opening a pull request. The ship workflow monitors the merge status to ensure safe, auditable delivery once verification passes and the PR is created.

Do I need a verification workflow to run before automating my pull request?

Yes, a verification workflow must pass before automating your pull request. The ship workflow is designed for phase- or milestone-driven development and acts as the bridge between completed local verification and the final merged PR.

What is the best way to manage branch pushes and PR creation for milestone-driven work?

The best way to manage branch pushes and PR creation for milestone-driven work is using an automated ship workflow. It auto-generates the PR body, pushes the branch, optionally triggers reviews, and tracks the merge for auditable delivery.