om-auto-fix-pr

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

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill om-auto-fix-pr-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-auto-fix-pr
Source: https://github.com/tkogut/agents-os-core/tree/main/global_skills/om-auto-fix-pr
Command: npx skills add https://github.com/tkogut/agents-os-core --skill om-auto-fix-pr-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Getting a pull request from open to merge-ready requires tedious manual cycles: merging the latest base branch, addressing review findings, fixing failing CI checks, and verifying UI changes. This Skill automates that entire loop for a given PR number without ever merging it itself. ## Core Features & Use Cases - Orchestrated stabilization loop: Coordinates review-autofix, CI stabilization, and UI QA sub-skills in a mandatory order until the PR is approvable, green, and QA-evidenced. - CI-only mode: Drives just CI green on a PR or a plain branch with no PR yet, skipping review, UI, and follow-ups. - Follow-up filing and handoff: Converts non-blocking review nits into tracked follow-up issues, normalizes labels, promotes drafts, and hands the merge-ready PR to the merge skill. - Use Case: A reviewer leaves feedback and CI is red on PR 123. Run the skill against that PR and it merges the latest base, fixes findings and CI failures with tests, files nits as follow-up issues, and leaves the PR labeled merge-ready. ## 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 get a pull request merge-ready automatically?▼

Run the skill with the PR number, for example om-auto-fix-pr 123. It merges the latest base branch, resolves conflicts and review findings via the autofix sub-skill, stabilizes CI, runs UI verification when relevant, and leaves the PR labeled merge-ready without merging it.

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

Use the --ci-only mode, such as om-auto-fix-pr 123 --ci-only, to run only the CI stabilization procedure. It classifies each failure as a real bug, test bug, flake, or infra issue, fixes real failures with tests, and never weakens or disables checks to go green.

Can I stabilize CI on a branch that has no pull request yet?▼

Yes. Use om-auto-fix-pr --ci-only --branch <name> to drive CI green on a plain branch. If an open PR already exists for that branch, the skill switches to PR mode automatically.

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

No. The skill never merges; it leaves the PR merge-ready with normalized labels and hands off to om-approve-merge-pr or om-merge-buddy, which re-check every gate including required checks and QA sign-off before merging.

What happens when the CI wait takes too long?▼

Every CI wait is capped by ci.maxWaitMinutes (default 40). On exhaustion the skill posts local validation results plus the still-pending checks, states that no further follow-up will come, drops the ci-monitoring label, and closes out rather than hanging.

How are non-blocking review findings handled?▼

Nits, low-severity items, and out-of-scope findings are filed as tracked follow-up issues via om-followup-issue-from-pr, idempotently so the same finding is never filed twice. Blocking findings are always fixed in the loop, never deferred.