lfx-pr-resolve

Resolve GitHub PR review feedback by reading threads, applying code changes, and committing.

8|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-pr-resolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lfx-pr-resolve
Source: https://github.com/linuxfoundation/lfx-skills/tree/main/lfx-pr-resolve
Command: npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-pr-resolve

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages and resolves PR feedback end-to-end by reading review threads, planning and applying code changes, committing with a detailed summary, and posting a concise PR-level update.

Core Features & Use Cases

  • Identify the target PR via number or URL, fetch all review threads, and determine unresolved items.
  • Apply validated code changes, commit with a structured message referencing reviewers, and post responses to each thread.
  • Post a single summary comment and re-request reviews to keep PRs moving.

Quick Start

Tell me the PR to address (by number or URL) and I will fetch unresolved threads, present a plan, and implement approved changes.

Frequently Asked Questions about lfx-pr-resolve

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

FAQPage Schema
How do I resolve GitHub pull request review feedback automatically?

To resolve GitHub PR review feedback automatically, fetch unresolved review threads, present a plan, apply code changes, and commit with a structured message. This end-to-end process also posts responses to threads and re-requests reviews.

How does automated PR feedback resolution work with the GitHub API?

Automated PR feedback resolution works by using the GitHub GraphQL API to authenticate, fetch review threads, and identify unresolved items. It then applies changes via signed commits and posts a summary comment to the pull request.

Can I use GraphQL to fetch unresolved pull request review threads?

Yes, you can use the GitHub GraphQL API to fetch unresolved pull request review threads. The process reads all threads, determines which items need action, and outputs a plan before applying any code changes.

What is the best way to manage code review changes and commit them to a pull request?

The best way to manage code review changes is to validate the requested updates, apply the code changes, and commit them with a detailed message referencing the reviewers. A concise PR-level summary is then posted.

Does resolving PR review comments require signed commits?

Yes, resolving PR review comments through this automated workflow ensures signed commits are used when applying code changes. This maintains commit integrity while updating the pull request across repositories.

Why do I need a plan before applying code updates to a pull request?

You need a plan before applying code updates to ensure all unresolved review feedback is correctly addressed. It validates the proposed changes and prevents incorrect modifications before committing to the pull request.