Auto-address PR Feedback

[strawgate]

Let's add a workflow which fires on PR feedback (i think there's a workflow like this in https://github.com/strawgate/kb-yaml-to-lens) that makes the minimum changes required to address the PR feedback, including resolving PR review comments, replying to pr review comments etc.

[github-actions]

Highly related (separate issues that significantly overlap or share scope):

• Add minimize-resolved-pr-reviews to tone down PR reviews #258 — This issue overlaps on automating PR review thread handling, but it is specifically about minimizing already-resolved review threads rather than auto-addressing new PR feedback.
  More detail

  Both focus on PR review lifecycle automation; Add minimize-resolved-pr-reviews to tone down PR reviews #258 implements `minimize-resolved-pr-reviews`, while this issue asks for broader feedback-driven actions (making fixes, resolving comments, and replying).
• Hide (minimize) completed review threads #47 — This issue also targets resolved review-thread management in PR workflows, but its scope is limited to hiding/minimizing completed threads.
  More detail

  The overlap is in working with PR review threads after resolution; the distinction is that this issue requests an end-to-end feedback response workflow rather than a presentation/tidying step.
• Small problem fixer workflow #59 — This issue is related as workflow automation for applying small fixes automatically, but it is framed around repository issues rather than PR review feedback.
  More detail

  Both emphasize minimal, targeted automated changes, but Small problem fixer workflow #59 concerns issue-driven fixes while this issue is specifically PR-feedback-triggered and includes review comment resolution/replies.

---

What is this? | From workflow: Duplicate Issue Detector

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

TL;DR: I recommend adding a new dedicated auto-address-pr-feedback workflow by reusing the mention-in-pr execution model, but triggering automatically on review feedback events and adding explicit guardrails for minimal diffs and selective thread resolution.

Recommendation

Build a new gh-aw workflow (separate from mention-in-pr) that runs on PR feedback events (pull_request_review submitted + pull_request_review_comment created), fetches unresolved review threads, applies the smallest safe fix, pushes once, then resolves only addressed threads. Keep mention-in-pr as explicit /ai opt-in.

Findings

1. The existing closest workflow is mention-in-pr, but it is opt-in via /ai, not automatic:

   • Trigger docs show /ai filtering for PR comments and inline review comments: gh-agent-workflows/mention-in-pr/README.md:23-25
   • Example trigger enforces /ai gate: gh-agent-workflows/mention-in-pr/example.yml:18-19
   • Dogfood trigger does the same: .github/workflows/trigger-mention-in-pr.yml:18-20

2. The underlying prompt already contains most behavior needed for “address feedback”:

   • It explicitly supports fixing code, pushing to PR branch, and resolving addressed review threads: .github/workflows/gh-aw-mention-in-pr.md:137-143
   • It imports the right safe outputs (add-comment, create-pull-request-review-comment, submit-pull-request-review, push-to-pull-request-branch, resolve-pull-request-review-thread): .github/workflows/gh-aw-mention-in-pr.md:14-18

3. Current safe outputs support:

   • PR conversation comments (add-comment): .github/workflows/gh-aw-fragments/safe-output-add-comment.md:2-5
   • New inline review comments with path+line+body (create-pull-request-review-comment): .github/workflows/gh-aw-fragments/safe-output-review-comment.md:2-10
   • Resolving review threads by thread node ID (resolve-pull-request-review-thread): .github/workflows/gh-aw-fragments/safe-output-resolve-thread.md:2-10

4. Related prior work:

   • Mention in PR for reviews #55 + PR Adjust mention-in-PR review comment guidance #57 already tightened mention-in-PR behavior around review/comment duplication.
   • Add a gh-aw workflow for fixing pr checks #53 added PR checks fixer (similar “automated fix then push” pattern, but for failed CI rather than review feedback).
   • Hide (minimize) completed review threads #47 addressed post-review hygiene (minimizing resolved review threads), which complements this request.

Verification

I validated the current behavior with repository searches and file inspection:

$ rg -n "pull_request_review:|pull_request_review_comment:|issue_comment:|startsWith\(github\.event\.comment\.body, '/ai'\)" --glob "*.{yml,md}"
.../gh-agent-workflows/mention-in-pr/example.yml:3:  issue_comment:
.../gh-agent-workflows/mention-in-pr/example.yml:5:  pull_request_review_comment:
.../gh-agent-workflows/mention-in-pr/example.yml:18:      startsWith(github.event.comment.body, '/ai') &&
.../.github/workflows/trigger-mention-in-pr.yml:3:  issue_comment:
.../.github/workflows/trigger-mention-in-pr.yml:5:  pull_request_review_comment:
.../.github/workflows/trigger-mention-in-pr.yml:18:      startsWith(github.event.comment.body, '/ai') &&

$ rg -n "resolve-pull-request-review-thread|create-pull-request-review-comment|submit-pull-request-review|add-comment" .github/workflows/gh-aw-fragments
.../safe-output-review-comment.md:3:  create-pull-request-review-comment:
.../safe-output-add-comment.md:3:  add-comment:
.../safe-output-submit-review.md:3:  submit-pull-request-review:
.../safe-output-resolve-thread.md:3:  resolve-pull-request-review-thread:

Detailed Action Plan

1. Create a new workflow shim (e.g., gh-agent-workflows/auto-address-pr-feedback/example.yml) with triggers:

   • pull_request_review types: submitted
   • pull_request_review_comment types: created
   • Optional workflow_dispatch for manual reruns.
     Model this after the mention-in-pr trigger wiring in gh-agent-workflows/mention-in-pr/example.yml:1-22, but remove /ai gating.

2. Add a new gh-aw source workflow in .github/workflows/gh-aw-auto-address-pr-feedback.md by adapting the instruction structure from .github/workflows/gh-aw-mention-in-pr.md:119-161:

   • Always load open review threads first (pull_request_read.get_review_comments)
   • Select only unresolved, non-outdated threads with actionable requests
   • Apply minimal patch set (single concern per commit/push)
   • Run required repo validation commands before push
   • Push once via push_to_pull_request_branch
   • Resolve only threads concretely addressed (resolve_pull_request_review_thread)

3. Add strict safety constraints in prompt text:

   • Do not change unrelated files
   • Do not resolve skipped/disputed threads
   • Skip/exit with add_comment when PR is from fork or feedback is non-actionable
   • Enforce “smallest possible change” and explicit test/command reporting.

4. (Optional but useful) Improve feedback-thread response semantics:

   • If you need first-class inline “reply” behavior, add/extend a safe output that supports replying to an existing review comment/thread (current create-pull-request-review-comment is path/line based: .github/workflows/gh-aw-fragments/safe-output-review-comment.md:9-10).

5. Document and compile:

   • Add a README entry similar to gh-agent-workflows/mention-in-pr/README.md
   • Run make compile to generate lock workflow
   • Run make lint and include output in the implementation PR.

Related Items

Type	Link	Relevance
Issue	#321	Current request
Issue	#55	Prior mention-in-pr review-flow behavior issue
PR	#57	Fixed duplicate comment/review behavior in mention-in-pr
Issue	#53	Introduced PR checks auto-fixer pattern
Issue	#47	Review-thread cleanup/minimization work
File	gh-agent-workflows/mention-in-pr/example.yml:1-22	Existing trigger/wiring baseline
File	.github/workflows/gh-aw-mention-in-pr.md:137-143	Existing fix/push/resolve behavior to reuse
File	.github/workflows/gh-aw-fragments/safe-output-resolve-thread.md:2-11	Thread resolution limits

---

What is this? | From workflow: Issue Triage

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[strawgate]

Let's do it on pull_request_review only and not on comment and let's use concurrency control to cancel existing flows