ship-pr

Commits finished changes, creates pull requests on GitHub or Forgejo, and monitors them until merge.

3|Updated Nov 8, 2014
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill ship-pr-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-pr
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/ship-pr
Command: npx skills add https://github.com/mintuz/.dotfiles --skill ship-pr-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping finished local work through a pull request involves many repetitive steps: committing with good messages, pushing, creating the PR, watching CI, fixing minor failures, and waiting for merge. This Skill automates that entire escort workflow across GitHub, Forgejo, and Gitea so you do not have to babysit the process. ## Core Features & Use Cases - Multi-forge support: Detects the hosting service from the origin remote and uses gh for GitHub or tea for Forgejo and Gitea, including API-based review and status-check gate evaluation. - Intentional committing: Separates finished work from unrelated changes, creates atomic commits with why-first messages, and refuses to ship unfinished work with failing tests or TODOs. - Persistent merge escort: Polls checks, reviews, mergeability, and branch protection in a bounded loop, automatically repairing minor CI failures and conflicts while escalating substantial ones to you. - Use Case: You finish a feature branch and say "ship it"—the Skill commits the changes, opens the PR, fixes a lint failure that CI catches, and keeps polling until you merge it. ## Quick Start Use the ship-pr skill to commit my current changes, open a pull request, and monitor it until it is merged.

Frequently Asked Questions about ship-pr

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

FAQPage Schema
How do I create and monitor a pull request until it is merged?

Invoke the skill with your finished changes on a feature branch. It commits the work, pushes the branch, creates the pull request with gh or tea, then polls checks, reviews, and mergeability until the forge reports the PR as merged.

Does this work with Forgejo or Gitea instead of GitHub?

Yes. The skill reads the origin remote host, probes authentication with gh and tea, and uses tea commands and API endpoints on Forgejo or Gitea for PR creation, reviews, commit status, and branch protection checks.

What happens when CI fails on my pull request?

Minor failures like formatting or lint issues are reproduced locally, fixed mechanically, committed, and pushed automatically. Substantial failures affecting behavior, APIs, or schemas are reported with root-cause evidence and resolution options, and the skill waits for your direction.

Will it merge the pull request automatically?

No. The user is treated as the merge owner. The skill reports when the PR is ready to merge and keeps polling, but merging, shared-history rewrites, and substantial conflict resolutions always require explicit user direction.

What happens if my changes include unfinished work?

The skill stops when it finds evidence of unfinished work, such as failing tests for unwritten behavior or TODO comments. It reports the evidence and asks whether to finish the work or ship only the finished commits.