workflow-address-feedback

Triage GitHub pull request review threads and apply code edits.

2|8|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/lugassawan/swe-workbench --skill workflow-address-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-address-feedback
Source: https://github.com/lugassawan/swe-workbench/tree/main/skills/workflow-address-feedback
Command: npx skills add https://github.com/lugassawan/swe-workbench --skill workflow-address-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the time-consuming, error-prone work of manually tracking PR review threads, applying fixes, replying appropriately, and resolving the threads so the reviewer can move on.

Core Features & Use Cases

  • Automated review-thread triage: fetches open GraphQL review threads and classifies each thread as ADDRESSED, CLARIFIED, or DEFERRED based on an interactive workflow, skipping threads that are already resolved or already clarified by the current user.
  • Owner-side patch workflow: creates an isolated worktree (via rimba when available or git worktree as fallback), applies edits using the Edit tool, and commits/pushes using the repository’s standardized commit-and-PR workflow.
  • Correct reply + resolve handling: posts per-thread replies (REST) and resolves addressed threads via the GraphQL resolveReviewThread mutation, then optionally prompts the reviewer for a re-check.
  • Resumable progress: saves triage state to /tmp so you can quit mid-stream and resume without losing which threads were already handled.

Quick Start

Run /swe-workbench:address-feedback <N> while authenticated with gh to systematically address open review threads on PR <N>.

Frequently Asked Questions about workflow-address-feedback

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

FAQPage Schema
How do I resolve multiple pull request review threads automatically?

Resolving multiple pull request review threads automatically requires a triage workflow that fetches open GitHub GraphQL review threads, classifies them, applies code edits, and executes resolveReviewThread mutations to close addressed comments.

What is the best way to triage and reply to GitHub PR review comments?

Triageing and replying to GitHub PR review comments is best handled by an automated workflow that classifies each thread, applies necessary code patches via an isolated worktree, posts REST replies, and resolves addressed threads to prompt the reviewer for a re-check.

Do I need GitHub CLI authentication to automate PR thread resolution?

Yes, GitHub CLI authentication is required to automate PR thread resolution. The workflow depends on gh CLI for fetching PR metadata, executing GraphQL review thread operations, and posting REST replies to coordinate commit and resolve actions.

Can I resume addressing PR review feedback if I quit mid-stream?

You can resume addressing PR review feedback if you quit mid-stream because the triage state is saved to a local /tmp file. This resumable progress ensures you do not lose track of which review threads were already handled.

How does commit and push work when fixing code review feedback in an isolated worktree?

Commit and push when fixing code review feedback works by creating an isolated git worktree, applying edits using the Edit tool, and committing and pushing changes using the repository's standardized commit-and-PR workflow before resolving the threads.