skills.rest
dobrinz123
dobrinz123COMMUNITY
Explore all skills by this author →
GitHub

gsd-ship

Push branches, create pull requests, and monitor merge status.

Updated Apr 9, 2026
Search Tags:#automation#git#github#merge#code-review#ci#pull-request
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-ship-dobrinz123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-ship
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-ship-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridge local completion to merged pull request by automating branch push, PR creation, review triggering, and merge tracking to reduce manual handoffs and human error.

Core Features & Use Cases

  • Branch publishing: Pushes the current work branch to the configured remote with correct naming and tracking.
  • Pull request generation: Creates a PR with an auto-generated body that summarizes the phase or milestone work.
  • Review and merge orchestration: Optionally requests reviewers, triggers review workflows, and monitors PR status until merge. Use Case: After verification passes for a project phase, run this skill to publish the branch, open the PR, initiate reviews, and follow the merge until the milestone is closed.

Quick Start

Run gsd-ship for phase 4 to push the branch, create a PR with an auto-generated body, optionally request reviewers, 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 pull request creation and merge readiness for a feature branch?▼

Automating pull request creation involves pushing the branch to the remote, generating a PR with a summarized body, optionally requesting reviewers, and monitoring the status until the merge is complete.

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 pull request is to automate branch push, PR generation, review triggering, and merge tracking to reduce manual handoffs and human error.

Do I need push access to automate PR creation and trigger GitHub code reviews?▼

Yes, automating PR creation and triggering GitHub code reviews requires push access to the remote repository, permission to create PRs, request reviewers, and compliance with branch and merge policies.

Can I automate requesting reviewers and monitoring PR status until merge?▼

Yes, you can automate requesting reviewers and monitoring PR status until merge by orchestrating review workflows and tracking the pull request state through to milestone closure.

When should I not use automated PR creation and merge orchestration?▼

You should not use automated PR creation and merge orchestration if your repository lacks branch and merge policies, or if your user account lacks push access and permission to create PRs.

Related Skills

Explore More Software Engineering Skills→
TMI-appsTMI-apps
2

push

Validate and push committed Git changes to a remote repository.

Official
Intermediate
ShmurdocShmurdoc

land-and-deploy

Merge pull requests, monitor CI pipelines, and verify production canary health.

Community
Advanced
LuisSambranoLuisSambrano
7

code-review

Perform systematic code review and static analysis across multiple programming languages.

Community
Advanced
pegasus-isipegasus-isi

pr

Create GitHub pull requests after validating CI status and branch integrity.

Official
Advanced