skills.rest
gesmith0606
gesmith0606COMMUNITY
Explore all skills by this author →
GitHub

gsd-ship

Push branches and create pull requests with auto-generated bodies and reviewer assignment.

Updated Aug 15, 2025
Search Tags:#automation#git#merge#pr#code-review#pull-request#continuous-integration
One-click install
npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-ship-gesmith0606
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/gesmith0606/nfl_data_engineering/tree/main/.claude/skills/gsd-ship
Command: npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-ship-gesmith0606

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bridges the gap between verified local work and a merged pull request by automating branch pushes, PR creation, reviewer requests, and merge tracking to remove manual shipping steps.

Core Features & Use Cases

  • Push and Publish: Push the current feature branch to the remote and prepare it for review.
  • PR Generation: Auto-generate a PR body from the workflow context and attach relevant metadata or links.
  • Review & Merge Tracking: Optionally assign reviewers, trigger review-related workflows or CI checks, and monitor merge readiness.
  • Use Case: After completing a feature and running local verification, run this Skill to create a standardized PR, request reviewers, and track CI until the branch is ready to merge.

Quick Start

Use the gsd-ship skill to push the current branch, create a PR with an auto-generated body, and request a review for merging.

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 from a local Git branch?▼

Automating pull request creation involves pushing your verified local branch to the remote repository and generating a PR with an auto-generated body. This workflow bridges local development and reviewable merge requests by removing manual shipping steps.

What is the best way to track CI checks and merge readiness for a GitHub PR?▼

Tracking merge readiness for a GitHub PR involves assigning reviewers and triggering review-related CI checks. You can monitor the merge status to ensure the branch meets all requirements before it is ready to merge into the main codebase.

How do I generate a pull request body from workflow context automatically?▼

Generating a PR body from workflow context takes your local verification data and attaches relevant metadata or links. This creates a standardized pull request description automatically, ensuring consistent context for reviewers without manual formatting.

Can I auto-assign reviewers when pushing a branch to a Git repository?▼

Auto-assigning reviewers when pushing a branch to a Git repository is supported during the PR creation step. You can optionally trigger reviewer requests to ensure the correct team members are notified for the merge request.

Does this automated PR workflow honor existing repository permissions?▼

Automated PR workflows honor repository permissions when pushing branches and requesting reviews. The process records merge status and triggers CI checks while respecting the access controls configured on your GitHub or Git-based repository.

Related Skills

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

push

Validate and push committed Git changes to a remote repository.

Official
Intermediate
PacificStudioPacificStudio
264

land

Enforce CI and branch-state checks before merging Git changes.

Official
Intermediate
az9713az9713
2

health

Integrate code quality tools to compute a composite health score.

Community
Intermediate
tribedotruntribedotrun
8

mando-pr

Create GitHub pull requests and trigger AI reviewers with CI monitoring.

Official
Advanced