fix-pr

Monitor CI statuses, resolve review comments, and merge pull requests via GitHub CLI.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/canpok1/claude-code-plugins --skill fix-pr-canpok1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-pr
Source: https://github.com/canpok1/claude-code-plugins/tree/main/plugins/base-tools/skills/fix-pr
Command: npx skills add https://github.com/canpok1/claude-code-plugins --skill fix-pr-canpok1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of checking and fixing issues in pull requests, including CI failures and review comments, and can automatically merge them when conditions are met.

Core Features & Use Cases

  • CI Status Monitoring: Watches and reacts to CI check statuses.
  • Review Comment Resolution: Identifies and helps address review comments.
  • Automated Merging: Merges PRs once all checks pass and reviews are approved.
  • Use Case: When a pull request fails its CI checks or receives review comments, this Skill can automatically attempt to fix the issues, re-run checks, and notify reviewers, streamlining the code review process.

Quick Start

Use the fix-pr skill to automatically address issues and merge the current pull request.

Frequently Asked Questions about fix-pr

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

FAQPage Schema
How do I automate fixing CI failures in a GitHub pull request?

To automate fixing CI failures in a GitHub pull request, this Skill monitors CI check statuses, identifies failures, and attempts automated resolutions before re-running checks and notifying reviewers.

Can I automatically merge a pull request after review comments are resolved?

Yes, you can automatically merge a pull request after review comments are resolved. This Skill manages review comments and performs conditional merging once all requirements and checks pass.

How does automated PR resolution handle different merge states like BLOCKED or DIRTY?

Automated PR resolution handles merge states like BLOCKED or DIRTY by interacting with GitHub CLI and APIs to evaluate the specific state and attempt issue resolution before proceeding with a conditional merge.

What's the best way to streamline code review and CI monitoring for GitHub PRs?

The best way to streamline code review and CI monitoring for GitHub PRs is using an automation Skill that watches CI statuses, addresses review comments, and merges PRs when conditions are met.

Does this PR automation tool work without additional dependencies?

Yes, this PR automation tool works without additional dependencies. It operates using internal scripts to interact directly with GitHub CLI and APIs for pull request management.

Why does my automated pull request merge remain BLOCKED?

Your automated pull request merge remains BLOCKED because the Skill evaluates merge states like BEHIND or BLOCKED and will not merge until all CI checks pass and review requirements are satisfied.