skills.rest
go-musicfox
go-musicfoxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

om-auto-fix-pr

Drives an open pull request to merge-ready through review autofix, CI stabilization, and UI verification.

2.6k|159|Updated Mar 8, 2021
Search Tags:#code review#pull request#orchestration#autofix#github automation#merge-ready#ci stabilization
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-auto-fix-pr-go-musicfox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-auto-fix-pr
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-auto-fix-pr
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-auto-fix-pr-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Open pull requests often stall in a loop of review comments, merge conflicts, red CI checks, and missing UI evidence. This Skill takes a PR number and autonomously iterates review-autofix, CI stabilization, and UI verification until the PR is approvable, green, and merge-ready — without ever merging it itself. ## Core Features & Use Cases - Orchestrated stabilization loop: Coordinates om-auto-review-pr (conflict resolution and review autofix), a built-in CI stabilization procedure (classify failures as real bug, test bug, flake, or infra, then fix and re-push), and om-auto-qa-pr for UI evidence, in a mandatory stage order. - CI-only mode: Run with --ci-only on a PR or a plain branch to drive checks green without the full review/UI loop. - Governance built in: Claims the PR with a three-signal lock, files non-blocking findings as follow-up issues, normalizes pipeline labels, promotes drafts, and hands off to om-approve-merge-pr — it never merges and never fakes green by weakening tests. - Use Case: A contributor's PR #123 has review comments, a conflict with main, and two failing checks. Run the Skill on PR 123 and it merges the latest base, fixes the findings, stabilizes CI, attaches UI evidence, files nits as follow-up issues, and leaves the PR labeled merge-queue. ## Quick Start Ask the agent to get PR 123 merge-ready using the om-auto-fix-pr skill.

Frequently Asked Questions about om-auto-fix-pr

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

FAQPage Schema
How do I automatically get a GitHub pull request merge-ready?▼

Invoke the skill with the PR number, for example om-auto-fix-pr 123. It merges the latest base branch, runs review autofix, stabilizes CI, verifies UI changes, normalizes labels, and hands the PR off to a merge skill without merging itself.

How do I fix failing CI checks on a pull request automatically?▼

Use the --ci-only mode, either on a PR (om-auto-fix-pr 123 --ci-only) or a plain branch (--ci-only --branch name). It classifies each failure as a real bug, test bug, flake, or infra issue, fixes the real ones with tests, pushes, and re-checks within a bounded wait budget.

Does this skill merge the pull request after fixing it?▼

No. It leaves the PR merge-ready with normalized labels and a summary comment, then hands off to om-approve-merge-pr or om-merge-buddy, which re-check every gate before merging. It also never adds qa-approved labels.

Can it handle pull requests from forks?▼

Yes. When the PR head is a fork that cannot be pushed to, the delegated review flow carries the work forward on a branch in the main repo and opens a replacement PR with a Supersedes line and credit to the original author.

What happens when the CI wait time runs out?▼

The run stops waiting at the configured ci.maxWaitMinutes limit (default 40 minutes), posts local validation results plus the still-pending checks, states that no further follow-up will come, and reports the PR as unverified rather than merge-ready.

Will it ever weaken or disable tests to make CI pass?▼

No. The CI procedure explicitly forbids going green by weakening tests, deleting assertions, skipping steps, or disabling checks. Failures are fixed with minimal changes and regression coverage, and flakes are confirmed via rerun before any action.

Related Skills

Explore More Software Engineering Skills→
tkoguttkogut
1

om-open-pr

Commits, pushes, and opens or reuses a labeled pull request for autonomous pipeline runs.

Community
Advanced
tomzxtomzx
5

merge-pr

Merge approved GitHub pull requests with passing CI checks.

Community
Advanced
tkoguttkogut
1

om-auto-fix-pr

Drives an open pull request to merge-ready through review autofix, CI stabilization, and UI verification.

Community
Advanced
NVIDIANVIDIA
22.3k

nemoclaw-maintainer-cross-issue-sweep

Scan open GitHub issues to find adjacent fixes and conflicts for a pull request.

Official
Advanced