skills.rest
mcampbellr
mcampbellrCOMMUNITY
Explore all skills by this author →
Website𝕏@mariocampbellrGitHub

gsd-ship

Create pull requests and trigger code reviews after verification passes.

Updated Apr 22, 2025
Search Tags:#code review#development workflow#automated workflow#merge preparation#PR creation
One-click install
npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-ship-mcampbellr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/mcampbellr/.dotfiles/tree/main/claude/.claude/skills/gsd-ship
Command: npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-ship-mcampbellr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of creating pull requests, running code reviews, and preparing for merge after verification passes, saving time and reducing manual errors.

Core Features & Use Cases

  • Automated PR Creation: Pushes a branch and creates a pull request with an auto-generated body.
  • Code Review Trigger: Optionally triggers a code review process.
  • Merge Preparation: Tracks the merge and closes the loop in the development workflow.
  • Use Case: After a verification phase, use this Skill to automatically create a pull request for code changes, trigger a review, and prepare for a smooth merge into the main branch.

Quick Start

Use the gsd-ship skill to ship the work after verification passes, specifying the phase number or milestone, e.g., '4' or 'v1.0'.

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 my code verification passes?▼

Automated PR creation pushes your branch and generates a pull request with an auto-generated body. This occurs after a verification phase passes, saving time and reducing manual errors in your software development workflow.

Can I automatically trigger a code review before preparing a branch merge?▼

Yes, you can trigger a code review process during merge preparation. The workflow optionally initiates a code review and tracks the merge to close the loop in the development cycle after verification succeeds.

What is the best way to streamline merge preparation in an automated development workflow?▼

Streamlining merge preparation involves automating branch management, PR creation, and code review triggering. This approach closes the development loop smoothly after verification passes, reducing manual errors and saving time.

How do I specify a milestone or phase number when automating PR creation?▼

You specify a milestone or phase number, such as '4' or 'v1.0', when initiating the workflow. This parameter contextualizes the automated pull request creation and merge preparation for that specific development phase.

Do I need specific branch management tools to use automated merge preparation?▼

Yes, automated merge preparation requires tools for branch management, pull request creation, and code review triggering. These tools enable the workflow to push branches and generate pull requests automatically.

Why does automated PR creation close the loop in a development workflow?▼

Automated PR creation closes the loop by tracking the merge status after triggering a code review. This ensures a smooth transition of code changes into the main branch once verification passes.

Related Skills

Explore More Software Engineering Skills→
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
fall-out-bugfall-out-bug
19

hotfix

Create a hotfix branch from main and deploy minimal P0 fixes.

Community
Advanced
burgebjburgebj

ship

Automate testing, code review, pull request creation, and deployment workflows.

Community
Advanced
alceupassosalceupassos

version-release

Automate software releases with Git tags, GitHub Release APIs, and version bumping.

Community
Advanced