gsd-ship

Automate branch pushing, pull request creation, and merge tracking for git workflows.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-ship-nnexai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ship
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-ship
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-ship-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead of finalizing code contributions by automating the transition from verified work to a merged pull request.

Core Features & Use Cases

  • Automated PR Lifecycle: Handles branch pushing, pull request creation with generated bodies, and merge tracking.
  • Workflow Integration: Bridges the gap between verification passes and production deployment.
  • Use Case: After completing a feature branch and passing all tests, use this skill to instantly open a PR and prepare the branch for final review and merging without manual CLI interaction.

Quick Start

Invoke the gsd-ship skill to push your current branch and create a pull request for the verified changes.

Frequently Asked Questions about gsd-ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git pull request creation after passing tests?

To automate pull request creation, you can use a workflow automation skill that pushes your current branch and generates a PR body for verified changes. This eliminates manual CLI interaction by handling the branch pushing and PR lifecycle automatically after tests pass.

What is the best way to automate branch pushing and merge tracking in a CI/CD workflow?

Automating branch pushing and merge tracking requires an orchestration tool that manages multi-step PR lifecycles within your CI/CD workflow. This approach bridges the gap between verification passes and repository integration by tracking the merge status automatically.

Can I use automated PR generation with existing GSD workflow definitions?

Yes, automated PR generation can be used with existing GSD workflow definitions. The automation operates within the context of verified task completion and requires integration with Codex agent orchestration to manage the multi-step pull request lifecycles seamlessly.

Does automated PR creation work without manual CLI interaction for git workflows?

Automated PR creation works without manual CLI interaction by handling the end-to-end shipping process internally. Once your feature branch passes all tests, invoking the automation instantly opens a pull request and prepares the branch for final review and merging.

When should I not use automated PR lifecycle management for git development?

You should not use automated PR lifecycle management when task completion has not been verified. The automation is designed to operate strictly within the context of verified work to ensure seamless transitions from local development to repository integration.

What problem does automating the end-to-end git shipping process solve?

Automating the end-to-end git shipping process solves the manual overhead of finalizing code contributions. It eliminates the need for manual branch pushing and pull request creation by automating the transition from verified work to a merged pull request.