fix-prs

Automate GitHub Pull Request repairs across organization repositories.

3|1|Updated Oct 9, 2025

Search Tags:#automation #workflow #ci/cd #code review #github #pr #repair

Ready to run

npx skills add https://github.com/OmniNode-ai/omniclaude --skill fix-prs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-prs
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/fix-prs
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill fix-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill tackles the common and time-consuming issues found in GitHub Pull Requests, such as merge conflicts, failing CI checks, and unaddressed review comments, by autonomously fixing them.

Core Features & Use Cases

Automated Conflict Resolution: Rebases PRs to resolve merge conflicts.
CI Failure Fixes: Integrates with a CI fixing sub-skill to address build and test failures.
Review Comment Addressing: Assists in resolving review feedback.
Use Case: A development team can use this skill to automatically clear out a backlog of PRs that are blocked by merge conflicts or failing CI, allowing reviewers to focus on the code logic rather than merge issues.

Quick Start

Run the fix-prs skill to scan all repositories for broken pull requests and attempt to fix them.

Frequently Asked Questions about fix-prs

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

FAQPage Schema

How do I automatically fix GitHub PRs with merge conflicts and failing CI checks?▼

Automating GitHub PR repair involves scanning repositories for blocked pull requests and autonomously rebasing them to resolve merge conflicts or addressing failing CI checks. This workflow prioritizes fixes to ensure PRs become merge-ready for reviewers.

What is the best way to clear a backlog of blocked GitHub pull requests?▼

The best way to clear a backlog of blocked GitHub pull requests is to autonomously repair merge conflicts, failing CI checks, and unaddressed review comments across an organization's repositories, allowing reviewers to focus on code logic rather than merge issues.

Can I use an automated workflow to address unaddressed review comments on GitHub pull requests?▼

Yes, you can use an automated workflow to address unaddressed review comments on GitHub pull requests. The autonomous repair process assists in resolving review feedback alongside fixing CI failures and merge conflicts across repositories.

Does autonomous PR repair work across an organization's GitHub repositories?▼

Yes, autonomous PR repair works across an organization's GitHub repositories. It scans all repositories for broken pull requests, prioritizes fixes, and utilizes sub-skills for detailed issue resolution to ensure they are merge-ready.

What types of failing CI checks can be autonomously fixed in a GitHub PR?▼

Failing CI checks involving build and test failures can be autonomously fixed in a GitHub PR. The repair workflow integrates with a CI fixing sub-skill to address these specific failures and bring the pull request back to a merge-ready state.