github-pr-fix

Analyze GitHub PR review feedback and CI failures to apply code changes.

132|13|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/holon-run/holon --skill github-pr-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-fix
Source: https://github.com/holon-run/holon/tree/main/skills/github-pr-fix
Command: npx skills add https://github.com/holon-run/holon --skill github-pr-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Fixes PRs by automatically analyzing review feedback and CI failures and applying targeted code changes back to the PR branch, shortening cycle time and improving consistency.

Core Features & Use Cases

  • Analyze PR review comments and CI failures to identify high-priority fixes.
  • Apply code changes, commit, and push to the PR branch, then prepare and publish review replies.
  • Produce artifacts (pr-fix.json, summary.md, manifest.json, publish-intent.json, publish-result.json) for traceability and automation.

Quick Start

Provide PR context and let the system automatically apply fixes to the PR branch.

Frequently Asked Questions about github-pr-fix

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

FAQPage Schema
How do I automatically fix CI failures and pull request review comments on GitHub?

To automatically fix CI failures and pull request review comments, this Skill analyzes GitHub PR feedback and applies targeted code changes directly to the PR branch. It then commits, pushes the fixes, and publishes review replies.

What is the best way to apply code changes from GitHub PR reviews automatically?

The best way to apply code changes from GitHub PR reviews automatically is by providing PR context to the system, which analyzes feedback and pushes commits back to the branch. It generates traceability artifacts like pr-fix.json and summary.md.

Do I need a GitHub token to automate pull request patching?

Yes, you need a GitHub token to automate pull request patching. The system uses the token with preferred tooling like ghx, or gh as a fallback, to collect PR context, apply fixes, and publish replies.

Can I use this to resolve merge conflicts and requested changes across GitHub pull requests?

Yes, you can use this to resolve merge conflicts and requested changes across GitHub pull requests. It identifies high-priority fixes from CI failures and review comments, then applies the necessary code changes to the branch.

What artifacts are produced when automating GitHub PR fixes?

When automating GitHub PR fixes, the system produces artifacts including pr-fix.json, summary.md, manifest.json, publish-intent.json, and publish-result.json. These files ensure traceability and support downstream automation.

Why are my automated pull request fixes not publishing replies to GitHub?

If automated pull request fixes are not publishing replies, check that your GitHub token has sufficient permissions. The system relies on this token with ghx or gh tooling to collect context and successfully publish review replies.