skills.rest
Eulga
EulgaCOMMUNITY
Explore all skills by this author →
GitHub

ship-develop

Automate feature branch shipping to develop with PR creation and Codex review.

Updated Mar 10, 2026
Search Tags:#automation#git#merge#branch-management#pull-request#codex-review#ship-develop
One-click install
npx skills add https://github.com/Eulga/discord-heatmap-bot-trading-calendar --skill ship-develop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-develop
Source: https://github.com/Eulga/discord-heatmap-bot-trading-calendar/tree/main/.agents/skills/ship-develop
Command: npx skills add https://github.com/Eulga/discord-heatmap-bot-trading-calendar --skill ship-develop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ship the current feature branch through the full GitHub flow to develop, automating verification, testing, PR creation or reuse, Codex review gating, and safe merge.

Core Features & Use Cases

  • End-to-end shipping: verify repo state, run tests, create/approve PRs, and merge when safe.
  • Codex review integration: request and wait for automated review feedback, blocking merges on findings when configured.
  • Safe branch cleanup: optionally delete local branches after successful merges to keep workspace clean.

Quick Start

Run the ship-develop workflow to push the current feature branch, create or reuse a PR into the target base, and trigger Codex review and automated checks.

Frequently Asked Questions about ship-develop

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

FAQPage Schema
How do I automate merging a Git feature branch into develop with PR review?▼

Automating a Git feature branch merge into develop involves a workflow that pushes your branch, creates or reuses a pull request, runs Codex review gating, and merges safely only when checks pass.

What is Codex review gating in a pull request workflow?▼

Codex review gating in a pull request workflow is an automated process that requests feedback on your code changes and blocks the merge if configured findings are detected, ensuring only reviewed code reaches the develop branch.

How do I detect a base branch and check for a dirty Git worktree before merging?▼

To detect a base branch and check for a dirty Git worktree before merging, the shipping workflow automatically inspects your repository state to identify the target base branch and blocks execution if uncommitted changes are found.

Can I automatically delete local Git branches after a pull request is merged?▼

Yes, you can automatically delete local Git branches after a pull request is merged using the optional local cleanup feature, which safely removes the merged branch to keep your workspace clean.

What is the best way to manage pull requests into develop for software teams using Git workflows?▼

The best way to manage pull requests into develop for Git workflow teams is to use an end-to-end automation tool that handles base-branch detection, PR creation or reuse, automated test execution, and Codex review integration for safe merges.

Related Skills

Explore More Software Engineering Skills→
good-ideagood-idea
3

using-git-worktrees

Create Git worktrees for isolated feature development and cleanup optionally deleting branches.

Community
Intermediate
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

staging-deployment-phase

Coordinate staging deployments with migrations, health checks, and verification.

Community
Intermediate
j-showj-show

review-helper

Review git diffs, apply fixes, and verify with pnpm check and test commands.

Official
Advanced
toqoztoqoz

github-release-pr

Automate GitHub release pull requests between development and production branches.

Community
Advanced