菜单
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.
Runs the local equivalent of the CI merge gate before you push. Detects which areas (Python, TypeScript, docs) your changes touch, auto-fixes what it can, then runs only those checks. Use when the user asks to run pre-push checks, get push-ready, verify changes before pushing or opening a PR, "make sure CI will pass", or check lint/tests/types locally.
Creates a GitHub pull request using the gh CLI. Use when the user asks to create, open, or submit a PR on GitHub.
Assess a published or in-progress documentation page for quality, accuracy, and voice compliance. Use before rewriting a page, during periodic health checks, when community signals point to confusion, or when comparing against competitor docs. Also triggers on "audit this page", "assess the docs", "what's wrong with this page", "check docs quality", "review this doc page".
Review documentation drafts for voice consistency, structure, and terminology before PR submission. Use after completing a draft, when checking if docs are ready to ship, or automatically after docs-writer produces output. Also triggers on "review this draft", "check my docs", "is this ready to ship", "review before merging".
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X", "document this feature".
| name | pr-feedback |
| description | Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request. |
Fetch PR review feedback and inline comments, categorize them, and present options to fix.
Auto-detect from the current branch:
gh pr view --json number -q .number
If that fails (detached HEAD, no tracking branch), ask the user for the PR number or URL.
Use the bundled script to fetch reviews, inline comments, and issue-level comments in one shot:
bash .agents/skills/pr-feedback/fetch-pr-feedback.sh <number> [--repo owner/repo]
<number> to auto-detect from the current branch.--repo when the PR is in a different repo than the current directory.The script returns JSON with three arrays:
reviews — top-level review summaries (non-empty bodies only)inline_comments — unresolved thread comments with upvotes/downvotes arrays (usernames who reacted), outdated flag, and diffHunk on the first comment in each threadcomments — issue-level commentsRead all the feedback, use your judgment to group related items, and present a numbered list of things to address. Keep each item to one line. Put the most impactful items first.
Use upvotes, downvotes, and the PR author's own replies to determine priority:
When presenting the list, annotate items you recommend fixing (based on the signals above) so the user can quickly confirm "all recommended" or cherry-pick.
Address only the confirmed items. After fixing, briefly note what changed — one line per item.