skills.rest
onelee85
onelee85COMMUNITY
Explore all skills by this author →
GitHub

gsd-ship

Push verified feature branches, create PRs, trigger reviews, and track merge status.

Updated Mar 27, 2026
Search Tags:#automation#shipping#ci-cd#code-review#branch-management#pull-request#gsd
One-click install
npx skills add https://github.com/onelee85/my-skills --skill gsd-ship
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/onelee85/my-skills/tree/main/gsd-ship
Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridge local completion to a merged PR after verification passes, removing manual steps and accelerating shipping.

Core Features & Use Cases

  • Automates pushing a branch after verification.
  • Auto-generates PR body and creates PR.
  • Optionally triggers review and tracks merge status.

Quick Start

Push your verified changes to a feature branch, then invoke the skill to auto-create a PR with an autogenerated body.

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 after passing local verification?▼

To automate PR creation after verification, the skill pushes your verified feature branch and auto-generates the PR body. This removes manual steps by bridging local completion directly to a created pull request.

Can I automatically trigger a code review and track merge status?▼

Yes, you can trigger a code review and track merge status. After creating the PR, the workflow optionally triggers the review process and actively monitors the merge status to ensure your verified changes are merged.

What is the best way to bridge local code completion to a merged pull request?▼

The best way to bridge local completion to a merged PR is through end-to-end shipping automation. This approach pushes your feature branch, generates the PR body, and tracks merge status after verification passes.

How do I auto-generate a PR body when pushing a feature branch?▼

You auto-generate a PR body when pushing a feature branch by invoking an automated shipping workflow after verification passes. The workflow handles the branch push and creates the PR with an auto-generated body to accelerate shipping.

Does branch management automation work without manual CI-CD pipeline triggers?▼

Branch management automation works by handling scripted workflow steps after verification. It pushes the verified branch and creates the PR automatically, removing the need for manual CI-CD pipeline triggers to start the shipping process.

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
yusaduymazyusaduymaz

gsd-ship

Push verified branches and open pull requests for merge tracking.

Community
Advanced
mt-krainskimt-krainski
1

wrap

Automate branch completion with code review, linting, testing, commits, and Pull Request creation.

Community
Advanced
a29paula29paul
1

ship

Automate code shipping with base branch detection, tests, version bumping, and PR creation.

Community
Advanced