skills.rest
TruCol270
TruCol270COMMUNITY
Explore all skills by this author →
GitHub

gsd-ship

Create pull requests and merge branches after verification checks pass.

1|Updated Apr 7, 2026
Search Tags:#automation#workflow#verification#merge#pr#ship#code-review
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-ship-trucol270
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-ship
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-ship-trucol270

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

  • End-to-end shipping: Pushes changes, creates PRs with auto-generated bodies, and optionally triggers reviews after verification.
  • Verification-driven merge: Waits for gsd-verify-work checks to pass before merging.
  • Auditable workflow: Tracks steps from branch creation to merge.

Quick Start

Push your changes, open a PR, and let the verification workflow handle the rest to auto-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 PR creation and merge after CI verification passes?▼

To automate PR creation and merge after CI verification, you need a workflow that pushes branches, drafts PR bodies, and enforces verification checks before merging. This ensures code is only merged when CI passes.

What is a verification-driven merge workflow for pull requests?▼

A verification-driven merge workflow for pull requests tracks steps from branch creation to merge, waiting for required CI checks to pass before merging. This provides an auditable record of code shipping.

How do I auto-generate PR bodies and trigger code reviews automatically?▼

You can auto-generate PR bodies and trigger code reviews automatically by using an end-to-end shipping automation tool that drafts the body upon PR creation and optionally triggers reviews for verification.

Can I enforce CI checks and code review before merging a branch automatically?▼

Yes, you can enforce CI checks and code review before merging a branch automatically by applying a controlled merge workflow that blocks merges until gsd-verify-work checks and optional reviews are completed.

What's the best way to track branch creation to PR merge for an auditable workflow?▼

The best way to track branch creation to PR merge for an auditable workflow is using an end-to-end automation process that records each step from push and PR generation through verification to the final merge.

Related Skills

Explore More Software Engineering Skills→
googlegoogle
291

Push to GitHub

Run unit tests and lint checks before pushing changes to GitHub.

Official
Intermediate
KrismithReddy12KrismithReddy12

land-and-deploy

Merge pull requests, trigger CI/CD pipelines, and validate production health.

Community
Advanced
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced
Simon-Copilot-StudioSimon-Copilot-Studio

github-code-review

Analyze git diffs and PR changes to generate structured code review feedback.

Community
Advanced