skills.rest
elsolal
elsolalCOMMUNITY
Explore all skills by this author →
GitHub

ship-workflow

Automate feature branch shipping to a pull request URL.

1|Updated Jan 20, 2026
Search Tags:#automation#git#workflow#release#pr#ship#continuous-delivery
One-click install
npx skills add https://github.com/elsolal/Skillz-Claude-Codex-And-More --skill ship-workflow-elsolal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-workflow
Source: https://github.com/elsolal/Skillz-Claude-Codex-And-More/tree/main/.claude/skills/ship-workflow
Command: npx skills add https://github.com/elsolal/Skillz-Claude-Codex-And-More --skill ship-workflow-elsolal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated shipping of a finished feature from a done branch state to a PR URL in a single non-interactive pass, reducing manual handoffs and distractions.

Core Features & Use Cases

  • Non-interactive by default — invoking /ship immediately progresses to PR creation unless blocked by real issues.
  • Stop for real blockers — merge conflicts, test failures, or critical review findings halt the flow.
  • Respect repository hygiene — never force-push; always run pre-commit hooks and validations; maintain bisectable commits.
  • End-to-end automation — merge main into the feature branch, run tests, update CHANGELOG, commit, push, and generate the PR URL.

Quick Start

Invoke /ship on a feature branch to automatically run tests, merge main, update CHANGELOG, commit, push, and open a PR.

Frequently Asked Questions about ship-workflow

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

FAQPage Schema
How do I automate creating a pull request from a feature branch in one step?▼

Automating pull request creation involves a workflow that merges the main branch, runs tests, updates the CHANGELOG, commits, pushes, and outputs a PR URL without manual intervention.

What is a non-interactive git workflow for shipping features?▼

A non-interactive git workflow automatically progresses from a finished feature branch to a PR URL, stopping only for real blockers like merge conflicts or test failures, reducing manual handoffs and distractions.

How do I keep git commits bisectable during release automation?▼

To keep git commits bisectable during release automation, the workflow runs pre-commit hooks and validations for every commit, ensuring repository hygiene without relying on force-pushes to bypass checks.

Does automated PR creation stop when tests fail?▼

Automated PR creation halts the shipping process when tests fail. The workflow stops for real blockers like merge conflicts, test failures, or critical review findings to ensure code stability.

What is the best way to update a CHANGELOG before opening a PR?▼

Updating a CHANGELOG before opening a PR is best handled by an automated workflow that merges main, runs tests, updates the CHANGELOG, commits, and pushes in a single non-interactive pass.

Can I use force-push in an automated feature release workflow?▼

Force-pushing is not used in automated feature release workflows. To respect repository hygiene, the workflow uses regular pushes and enforces pre-commit hooks to maintain clean, bisectable commits.

Related Skills

Explore More Software Engineering Skills→
MayaDispelerMayaDispeler
3

git-workflow

Enforce git commit message formats, branch naming, and pull request guidelines.

Community
Advanced
hypeJunctionhypeJunction
1

iterate-pr

Iterate on open pull requests to resolve CI failures and review feedback.

Community
Advanced
DevelopersGlobalDevelopersGlobal
65

ci-cd-pipelines

Automate CI/CD pipelines with quality gates and deployment processes.

Official
Advanced
AndrewLi0420AndrewLi0420

ship

Merge base branches, run tests, bump VERSION, update CHANGELOG, and create PRs.

Community
Advanced