菜单
Use when asked to look at or address feedback on a PR. Fetches Copilot feedback from both inline threads and review bodies, skips hidden comments, then evaluates and fixes the valid ones.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/keybase/client --skill address-pr-feedback命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when writing, fixing, or adding e2e flow tests for the Keybase app — desktop (Playwright) or iOS (Appium + WebdriverIO). Covers testID conventions, navigation patterns, common pitfalls, and the two-harness structure.
This skill should be used when the user asks to "compare screenshots", "visual diff", "check for visual regressions", "before and after screenshots", "did the UI change", or mentions comparing the desktop app UI between branches or before/after a change. Also triggered by "take baseline", "take current", or "compare against baseline".
Use when hunting redundant, duplicated or looping RPCs in the Keybase client — after a rate-limit error, a service log that rotates every few minutes, a slow or hot app, or to prove a caching fix actually reduced calls. Covers capturing a clean service log against a locally built service and reading it.
正在显示 SKILL.md
| name | address-pr-feedback |
| description | Use when asked to look at or address feedback on a PR. Fetches Copilot feedback from both inline threads and review bodies, skips hidden comments, then evaluates and fixes the valid ones. |
./.claude/skills/address-pr-feedback/get-copilot-feedback.sh [pr-number]
If no PR number is given, it uses the current branch's PR.
Copilot reports findings in two different places, and the script reads both:
[OUTDATED].Comments generated: 0 and puts
its real findings in the review body instead, under ### Suppressed comments. These never
appear as threads.An empty "Inline review threads" section does NOT mean the review was clean. That is the
trap this skill exists to avoid: a thread-only query returns nothing and the PR looks unreviewed
when Copilot in fact filed a finding in the body. Always read both sections before concluding
there is no feedback. If both are empty, check that Copilot has actually reviewed
(gh pr view <n> --json reviews) rather than assuming it found nothing.
The script deliberately strips Copilot's per-file summary table — it restates the diff and carries no findings. It keeps the headline verdict, the one-line concern beneath it, and the suppressed-comments block.
For each finding:
[OUTDATED] ones this matters most: the diff position moved,
but the underlying issue often still exists — find the corresponding spot and evaluate there.
A body finding cites path:line from an older push; re-locate it by symbol, not line number.Do not post replies to GitHub comment threads. Just fix the code.
A comment is hidden only when its thread is resolved or minimized on GitHub. Those are skipped automatically and need no action. Outdated is not hidden — evaluate those normally.