pr-ship

Stage local changes from a mixed worktree and publish a draft PR.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Hyd3-14/dotfiles --skill pr-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-ship
Source: https://github.com/Hyd3-14/dotfiles/tree/main/home/.agents/skills/pr-ship
Command: npx skills add https://github.com/Hyd3-14/dotfiles --skill pr-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship local changes with confidence by moving uncommitted work from a mixed worktree into a controlled flow that ends in a draft PR, preventing accidental leaks or overwrites.

Core Features & Use Cases

  • Scoped scope verification and selective staging to ensure only intended changes are included.
  • End-to-end workflow from local edits to a draft PR, with explicit reporting of results and caveats.
  • Reusable pattern for coordinating commits, pushes, and PR creation in collaborative projects.

Quick Start

Run pr-ship with a defined scope to ship the current changes as a draft PR.

Frequently Asked Questions about pr-ship

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

FAQPage Schema
How do I safely ship local changes to a draft PR without leaking unintended files?

To safely ship local changes to a draft PR, use a workflow that verifies scope and selectively stages files from your mixed worktree before committing and pushing. This prevents accidental inclusion of unintended edits.

What is the best way to separate staged commits from a mixed worktree?

The best way to separate staged commits from a mixed worktree is through selective staging, which verifies the scope of your changes and isolates only the intended files before committing and publishing them.

How do I create a draft PR from uncommitted local edits?

To create a draft PR from uncommitted local edits, apply a workflow that selectively stages the intended changes, commits them, pushes to a remote branch, and creates the draft PR with verifiable reporting.

Can I automate the process of selectively staging and pushing to a draft PR?

Yes, you can automate the end-to-end process of selectively staging, committing, pushing, and creating a draft PR. This workflow ensures only scoped changes are published while reporting results and caveats.

Why should I use selective staging before creating a draft PR?

You should use selective staging before creating a draft PR to prevent accidental leaks or overwrites. It verifies the scope of your worktree, ensuring only explicitly intended changes are included in the commit.

Does the draft PR workflow provide reporting on what changes were shipped?

Yes, the draft PR workflow provides explicit reporting of results and caveats after pushing. This confirms exactly which scoped changes were committed and published from your local worktree.