om-pr-autopilot

Diagnose an open pull request's state and chain the matching review, fix, QA, and merge skills.

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-pr-autopilot-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-pr-autopilot
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-pr-autopilot
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-pr-autopilot-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Open pull requests stall in unclear states: unfinished plan steps, missing reviews, unresolved conversations, red CI, base conflicts, or absent QA evidence. This Skill diagnoses exactly what state one PR is in and drives it to merge-ready by dispatching the right companion skills in the right order, instead of making you guess which workflow to run. ## Core Features & Use Cases - State Diagnosis: Collects ten read-only signals (plan progress, diff scope, review decision, CI, mergeability, labels, QA evidence, claim state) into a single PR State Report. - Ordered Skill Chaining: Matches the diagnosis against a state matrix and invokes companion skills verbatim in order — implementation, merge-readiness, QA, then merge — re-checking cheap signals between steps. - Safe Autonomy Controls: Supports --dry-run, --confirm, --allow-merge (off by default), --force, and --max-iterations, with claim locking, stale-lock recovery, and a bounded CI follow-up window. - Use Case: You return to PR #4321 after the weekend and do not know what is left. Run the autopilot to get a full diagnosis, an executed fix-and-review chain, and a published summary comment with labels, QA verdict, and follow-up issues. ## Quick Start Ask the agent to drive PR 4321 to completion with a dry run first, for example: run om-pr-autopilot on PR 4321 with --dry-run and show me the diagnosis and planned chain.

Frequently Asked Questions about om-pr-autopilot

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

FAQPage Schema
How do I finish a pull request that is stuck in an unknown state?

Run the autopilot with the PR number; it reads ten state signals, classifies the PR against a state matrix, and executes the matching chain of continue, fix, review, QA, and merge skills in order. Use --dry-run first to see the diagnosis and planned chain without mutating anything.

What is the difference between om-pr-autopilot and om-auto-fix-pr?

om-pr-autopilot is a dispatcher that diagnoses a PR and decides which skills to run; om-auto-fix-pr is one of the delegated skills that performs review, autofix, and CI repair. Use the autopilot when you do not know the PR's state, and the specific skill when you already do.

Can the autopilot merge a pull request automatically?

No, merging is off by default. The chain stops at merge-ready unless you pass --allow-merge, and even then the merge only proceeds when required checks are green and the QA gate is satisfied.

What happens when the PR belongs to another author or a fork?

Another author's PR receives review plus handoff rather than autofix, unless you explicitly request the autofix chain. For a fork you cannot push to, the delegated review flow opens a credited carry-forward replacement PR reassigned to the original author.

Why does the run report before CI finishes?

Reporting is decoupled from CI so a crashed monitoring process never leaves a stranded, unlabeled PR. The summary comment, labels, and verdict publish immediately, pending checks are disclosed, and any CI wait is bounded by a configurable budget with a clean bail-out.

What are the limitations of the PR autopilot?

It never re-implements delegated work, never opens PRs itself, and stops on hard blockers like do-not-merge or failed QA. It also requires the companion om-* skills to be installed; a missing companion stops the run rather than being improvised.