pr-address

Automates pull request review feedback resolution via fixup commits and GitHub API interactions.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/EdgeApp/edge-dev-agents --skill pr-address-edgeapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-address
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/pr-address
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill pr-address-edgeapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, jq, and includes scripts (resource) components.

What problem does it solve?

This skill streamlines the pull request review process by automating the application of fixup commits, replying to review threads, and managing the complex state of PR feedback, ensuring a clean and efficient development loop.

Core Features & Use Cases

  • Automated Fixup Management: Automatically applies code changes as fixup commits and slots them next to their target commits to maintain a clean history.
  • Intelligent Feedback Processing: Fetches unresolved threads, replies to comments, and marks items as addressed using machine-readable markers.
  • Workflow Guardrails: Enforces strict ownership rules, ensuring that history is only rewritten on PRs owned by the user and preventing unauthorized thread resolution.

Quick Start

Invoke the pr-address skill to fetch all unresolved feedback for the current pull request and begin the automated fixup and reply process.

Frequently Asked Questions about pr-address

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

FAQPage Schema
How do I automate pull request review feedback resolution?

Automating pull request review feedback resolution involves fetching unresolved GitHub threads, applying targeted fixup commits, and replying to comments via the GitHub API. This skill manages that entire loop to maintain a clean development workflow.

Do I need the GitHub CLI and jq to manage fixup commits?

Yes, you need the GitHub CLI and jq to manage fixup commits, alongside git. These dependencies are required to securely handle repository state, interact with the GitHub API, and parse machine-readable markers for thread resolution.

Can I use this to rewrite git history on any collaborative pull request?

No, you cannot use this to rewrite git history on any collaborative pull request. Strict workflow guardrails enforce ownership rules, ensuring history is only rewritten on PRs owned by the user to prevent unauthorized thread resolution.

What is the best way to slot fixup commits next to target commits?

The best way to slot fixup commits next to target commits is through automated fixup management. This process applies code changes as fixup commits and automatically reorders them alongside their target commits to maintain a clean history.

How does intelligent feedback processing mark GitHub review threads as addressed?

Intelligent feedback processing marks GitHub review threads as addressed by using machine-readable markers. It fetches unresolved threads, applies the corresponding fixup commits, replies to comments, and updates the thread state securely.