ship

Automate shipping code changes from local work to merged PRs with guardrails.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/oobagi/jflow --skill ship-oobagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/oobagi/jflow/tree/main/skills/ship
Command: npx skills add https://github.com/oobagi/jflow --skill ship-oobagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch and merge workflows are manual, error-prone, and slow; this skill standardizes pre-flight checks, branch hygiene, and PR generation to accelerate shipping changes reliably.

Core Features & Use Cases

  • Pre-flight checks: run lint/build if present and halt on failures.
  • Dirty-tree guard: detect unrelated WIP changes and prompt for handling.
  • Branching & PR workflow: create feature branches, commit with descriptive messages, push, and open PRs with proper references.
  • CI integration: wait for checks and provide status, with safe rollback guidance.

Quick Start

Ship the current changes by performing pre-flight checks, reviewing git status, creating a feature branch, committing with a descriptive message, pushing to origin, and opening a PR with appropriate Closes notes.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git branch creation and pull request generation?

To automate git branch creation and pull request generation, this skill standardizes the workflow by creating feature branches, committing with descriptive messages, pushing to origin, and opening PRs with proper issue references. It accelerates shipping changes reliably.

What is the best way to manage pre-flight lint and build checks before opening a pull request?

Managing pre-flight lint and build checks before opening a pull request is handled by enforcing guardrails that run available lint/build operations and halt the shipping workflow immediately upon detecting failures, ensuring code quality before PR creation.

How does dirty-tree protection work when committing changes to a feature branch?

Dirty-tree protection works when committing changes to a feature branch by detecting unrelated WIP changes in your local work and prompting you for handling instructions before proceeding with the branch and PR workflow.

Can I use this workflow to verify CI integration status after pushing a pull request?

Yes, you can use this workflow to verify CI integration status after pushing a pull request. It waits for CI checks to complete, provides the resulting status, and offers safe rollback guidance if the integration fails.

Does this branching and PR workflow support GitHub-style code reviews for software development teams?

Yes, this branching and PR workflow supports GitHub-style code reviews for software development teams. It applies to development teams performing feature work and enforces branching discipline across CI-integrated merges.

What happens if pre-flight checks fail during the code shipping workflow?

If pre-flight checks fail during the code shipping workflow, the process halts immediately to prevent broken code from being pushed. This guardrail ensures only lint and build compliant changes proceed to feature branch creation and PR generation.