Agent Skills › pydantic/pydantic-ai › address-feedback

address-feedback

GitHub

自动查找并处理当前分支PR中的未解决评审意见，包括收集上下文、分类讨论、修复代码、向用户汇报变更并获取批准，最后通过API回复评论并关闭线程。

.claude/skills/address-feedback/SKILL.md pydantic/pydantic-ai

Trigger Scenarios

需要清理PR评审评论用户要求解决代码审查反馈

Install

npx skills add pydantic/pydantic-ai --skill address-feedback -g -y

More Options

Non-standard path

npx skills add https://github.com/pydantic/pydantic-ai/tree/main/.claude/skills/address-feedback -g -y

Use without installing

npx skills use pydantic/pydantic-ai@address-feedback

指定 Agent (Claude Code)

npx skills add pydantic/pydantic-ai --skill address-feedback -a claude-code -g -y

安装 repo 全部 skill

npx skills add pydantic/pydantic-ai --all -g -y

预览 repo 内 skill

npx skills add pydantic/pydantic-ai --list

SKILL.md

Frontmatter

{
    "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."
}

Address PR Review Feedback

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:
- If it's clear how to address (implement the suggestion, or decide it shouldn't be done with a clear reason): fix it.
- If a maintainer or PR author has already weighed in on the thread (e.g. explaining why a suggestion doesn't apply), respect that guidance.
- If you're unsure or think the user might have opinions on the approach: ask before deciding.
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.