メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/pydantic/pydantic-ai --skill address-feedbackコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), 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, defer capability loading, stream output, define agents from YAML, or test agent behavior.
Add a new provider API capability (prompt caching, strict/structured tool calling, thinking/reasoning effort, service tier, safety settings, logprobs, etc.) to Pydantic AI. Use when wiring a provider feature through the library — it enforces reasoning from the existing cross-provider abstraction before designing anything, and picking default-on vs opt-in deliberately. Not for adding a new model id (that's a different flow) or a bug fix.
What to do when you open a PR and every time you push — label the PR, run a local review, watch CI to green, triage every review comment to a reply and a reaction, and escalate genuine design trade-offs to maintainers. Use whenever you open a PR or push a commit to one.
SKILL.md を表示中
SOC 職業分類に基づく
| 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.
