fix-reviews

Detect pull requests with requested changes and launch fixer agents via git worktrees.

5|1|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ncukondo/reference-manager --skill fix-reviews-ncukondo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-reviews
Source: https://github.com/ncukondo/reference-manager/tree/main/.claude/skills/fix-reviews
Command: npx skills add https://github.com/ncukondo/reference-manager --skill fix-reviews-ncukondo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects PRs with changes requested and automatically spawns fixer agents to address reviewer feedback, reducing cycle time and manual toil.

Core Features & Use Cases

  • Automated PR remediation: detects open PRs with CHANGES_REQUESTED state and queues dedicated agents to implement fixes.
  • Orchestration under pane limits: coordinates multiple agents using tmux panes with a configurable cap to avoid resource contention.
  • Worktree-based isolation: creates and uses separate git worktrees per PR for safe, parallel edits.

Quick Start

Run the fix-reviews skill to automatically detect PRs needing changes and start fixer agents.

Frequently Asked Questions about fix-reviews

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

FAQPage Schema
How do I automatically fix pull requests that have changes requested?

To automatically fix pull requests with changes requested, this skill detects open PRs in that state and spawns dedicated fixer agents to implement the requested changes. It coordinates multiple agents using tmux and git worktrees to isolate edits per PR.

Can I use git worktrees to isolate parallel fixes for multiple pull requests?

Yes, you can use git worktrees to isolate parallel fixes for multiple pull requests. This skill creates a separate git worktree per PR, allowing multiple fixer agents to safely implement changes concurrently without interfering with each other.

How does tmux orchestration manage resource limits when spawning multiple code review fixer agents?

Tmux orchestration manages resource limits by enforcing a configurable pane cap when spawning code review fixer agents. This coordination prevents resource contention by limiting the number of agents running simultaneously across tmux panes.

Do I need GitHub CLI and Git installed to automate pull request remediation?

Yes, you need GitHub CLI and Git installed to automate pull request remediation. This skill relies on GitHub CLI to detect PRs with changes requested and uses Git to manage worktrees for isolating edits.

What is the best way to reduce manual toil when addressing reviewer feedback on GitHub pull requests?

The best way to reduce manual toil when addressing reviewer feedback is automating PR remediation. This skill detects PRs with changes requested and automatically launches fixer agents to implement the requested changes end-to-end.

Why does the fix-reviews agent use tmux panes instead of standard background processes for PR workflows?

The fix-reviews agent uses tmux panes instead of standard background processes to coordinate multiple fixer agents under a configurable pane limit. This tmux-based orchestration manages resources and isolates edits per PR using git worktrees.