fix-failed-pr

Repair GitHub Pull Requests with failed CI checks or merge conflicts.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/bismuthdigital/claude-project-template --skill fix-failed-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-failed-pr
Source: https://github.com/bismuthdigital/claude-project-template/tree/main/.claude/skills/fix-failed-pr
Command: npx skills add https://github.com/bismuthdigital/claude-project-template --skill fix-failed-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, ruff, mypy, pytest, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically finds, claims, and repairs GitHub Pull Requests that have failed Continuous Integration checks or have merge conflicts, ensuring smoother code integration.

Core Features & Use Cases

  • Automated PR Triage: Identifies PRs needing attention due to CI failures or merge conflicts (DIRTY status).
  • Conflict Resolution: Attempts to automatically resolve merge conflicts by rebasing and applying defined strategies for different file types.
  • CI Failure Diagnosis: Diagnoses and attempts to fix CI failures similar to a /ci-review skill.
  • Safe Concurrent Operation: Uses a work queue to ensure multiple agents can safely claim and repair different PRs simultaneously.
  • Use Case: An agent automatically picks up a PR that failed its tests, rebases it onto the latest main branch, resolves a minor conflict in a test file, and pushes the fix, allowing it to be merged.

Quick Start

Use the fix-failed-pr skill to automatically find and repair a PR that is failing CI or has merge conflicts.

Frequently Asked Questions about fix-failed-pr

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

FAQPage Schema
How do I automatically fix GitHub pull requests that failed CI checks?

To automatically fix GitHub pull requests that failed CI checks, you can use an automated agent to claim the PR, diagnose the failures, apply fixes, and push the re-submitted PR for merging.

Can I automatically resolve merge conflicts in pull requests via rebase?

Yes, you can automatically resolve merge conflicts in pull requests by claiming the PR, rebasing it onto the latest main branch, applying defined file-type strategies, and pushing the resolved result.

What is the best way to handle concurrent agents repairing multiple failed PRs?

The best way to handle concurrent agents repairing multiple failed PRs is using a work queue mechanism, which ensures multiple agents safely claim and repair different pull requests simultaneously without overlap.

Do I need GitHub Actions to run automated pull request triage and conflict resolution?

You need git and gh dependencies along with ruff, mypy, and pytest to run automated pull request triage, diagnosing CI failures and resolving conflicts within your software engineering workflow.

How does an agent diagnose and fix CI failures before re-submitting a PR?

An agent diagnoses and fixes CI failures by claiming the broken PR, identifying the test or linting errors, applying the necessary code fixes, and re-submitting the updated pull request for merging.