workflow-pr-review-followup

Re-run reviewer agent on updated PR diffs and deduplicate feedback against existing GitHub review threads.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, rimba, git, awk, sed, graphql.

What problem does it solve?

It prevents repeated, noisy PR reviews by re-checking whether prior reviewer feedback was actually addressed and then adding only genuinely new issues as inline comments.

Core Features & Use Cases

  • Targeted follow-up reviews: Re-runs the reviewer agent against the updated PR diff after feedback changes.
  • Thread deduplication: Fuzzy-matches against existing review threads (path/line proximity plus content similarity) and avoids reposting duplicates.
  • Review decision enforcement: Submits exactly one inline review outcome (APPROVE or COMMENT) based on the reviewer footer contract, with an out-of-diff blocking-scope verdict for context.
  • Optional ticket context: Automatically prepends ticket context when the PR references common ticket formats.

Quick Start

Use the workflow-pr-review-followup skill to re-check PR #123 after the owner addresses feedback.

Frequently Asked Questions about workflow-pr-review-followup

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

FAQPage Schema
How do I automate GitHub pull request follow-up reviews without posting duplicate inline comments?

Automated pull request follow-up reviews prevent duplicate inline comments by re-running a reviewer agent against the latest diff and deduplicating results against existing GitHub review threads using fuzzy path and line matching.

What is the best way to re-check if PR review feedback was addressed in a new commit?

To re-check if PR review feedback was addressed, the workflow re-runs the reviewer agent on the updated diff, parses the reviewer footer for an APPROVE or COMMENT verdict, and posts only genuinely new issues as inline comments.

Does this PR review automation require GitHub authentication and a specific CLI tool?

Yes, GitHub PR review automation requires GH authentication and the gh CLI to fetch pull request state, query existing review threads via GraphQL, and post scoped inline comments.

How does the deduplication mechanism work when re-reviewing a GitHub pull request?

The deduplication mechanism works by fuzzy-matching new review findings against existing GitHub threads using Jaccard-based content similarity and path/line proximity to avoid reposting duplicate inline comments.

Can I use this workflow orchestration tool for pull requests that are closed or merged?

No, this workflow orchestration tool includes a strict PR open-state guard, meaning the pull request must be open for the reviewer agent to create a worktree, re-run the diff analysis, and post follow-up comments.

How are blocking issues outside the diff handled during automated PR re-reviews?

Blocking issues outside the diff are handled by submitting an out-of-diff blocking-scope verdict for context, while the review decision itself is enforced strictly through inline comments scoped to repo-relative paths.