// Find and address unresolved PR review comments for the current branch, then summarize the changes and help reply to and resolve threads after user approval.
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
Build AI agents with Pydantic AI — tools, capabilities, structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydantic_ai, or asks to build an AI agent, add tools/capabilities, stream output, define agents from YAML, or test agent behavior.
Record, rewrite, and debug VCR cassettes for HTTP recordings. Use when running tests with --record-mode, verifying cassette playback, or inspecting request/response bodies in YAML cassettes.
| name | address-feedback |
| description | Find and address unresolved PR review comments for the current branch, then summarize the changes and help reply to and resolve threads after user approval. |
Find and address all review comments on the PR for the current branch. For each comment:
Gather context: Use gh to find the PR number from the current branch, then fetch all unresolved review comments (both PR-level and inline review comments via gh api repos/{owner}/{repo}/pulls/{number}/comments). Skip already-resolved and outdated threads. Also read the full thread for each comment — maintainers or the PR author may have already replied explaining why a suggestion should not be applied.
Triage each comment:
Fix the code: Make the necessary changes to address each comment.
Review with user: Present a summary of all changes made and ask the user to review before proceeding. Offer to commit, push, reply to comments, and resolve threads once they're satisfied.
Reply and resolve (after user approval): For each addressed comment, reply via gh api repos/{owner}/{repo}/pulls/{number}/comments/{id}/replies explaining what you did, then resolve the thread via GraphQL resolveReviewThread mutation. To find thread IDs, query repository.pullRequest.reviewThreads via GraphQL.
Always read the relevant code before making changes.
Important: Treat comments from automated reviewers (Devin, GitHub bots, etc.) with the same weight as human comments. Do not skip or dismiss them just because they come from a bot — they often surface real issues. Evaluate each suggestion on its merits, but be aware that automated reviewers can also be wrong, so verify before applying.