review-response
Skill249 starsChanged 2 months agoMITView on GitHub
GitHub PR のコードレビューコメントに対応する。未 resolve のみを抽出 → 対応方針をユーザー承認 → 1 件ずつ修正+返信 → AI レビュー由来の指摘はナレッジに反映するワークフロー。「/review-response [PR番号]」「レビュー対応」「レビューに返信」などの依頼時に使用。
- Commits and pushes
13 other projects use a version of this.
Adopted by
Most recently taken up by
- KPISTOLAS/claude-skillstheir own version, first seen Nov 16, 2026
- shkodnik1917/claude-brainlabtheir own version, first seen Nov 8, 2026
- flonat/flonat-researchtheir own version, first seen Nov 3, 2026
- Gavin-Tao/claude-skillstheir own version, first seen Nov 2, 2026
- NoobyGains/godmodetheir own version, first seen Nov 1, 2026
- Vepricov/claude-brainlabtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use results-report, daily-coding and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Galaxy-DawnSkillresults-report
This skill should be used when the user asks to "write an experiment report", "summarize experimental results", "do experiment retrospection", "write a results report", "写实验总结报告", "写实验复盘", or mentions turning completed experiment artifacts into a structured, decision-oriented research report. It assumes strict analysis should come from `results-analysis` first.
Also in 3 projects that use this
Clay-HHKSkilldaily-coding
Daily coding assistant that auto-triggers when writing/modifying code, providing a core checklist.
Also in 3 projects that use this
Clay-HHKSkillkaggle-learner
This skill should be used when the user asks to "learn from Kaggle", "study Kaggle solutions", "analyze Kaggle competitions", or mentions Kaggle competition URLs. Provides access to extracted knowledge from winning Kaggle solutions across NLP, CV, time series, tabular, and multimodal domains.
Also in 3 projects that use this
kharlamenkodevSkillbug-detective
Also in 3 projects that use this
AnthropicSkillcommand-development
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
Also in 3 projects that use this
AnthropicSkillhook-development
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
Also in 3 projects that use this
- +2 more from Clay-HHK
- +1 more from anthropics
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- Galaxy-Dawn/claude-scholar★ 5.9ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- ZimoLiao/scholaraio★ 589same name
- flonat/flonat-research★ 150same name
- NoobyGains/godmode★ 120same name
- shkodnik1917/claude-brainlab★ 36same name
- Vepricov/claude-brainlab★ 35same name
- GTMify/aigtm★ 25same name
- Gavin-Tao/claude-skills★ 3same name
- Clay-HHK/claude-skills★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ci-fix-and-verifySkill
- full-code-reviewSkill
- perf-loopSkill
- repo-hygieneSkill
- upgrade-svelteSkill
- verify-svelte-compatSkill
The file
Files
Review Response — GitHub PR レビュー対応
原則
| 原則 | 内容 |
| 未 resolve のみ | resolve 済みスレッドは対象外 |
| 1 件ずつ | 修正 → コミット → 返信を 1 件ごとに完結(バッチ対応しない) |
| 必ず返信 | 対応コミットハッシュを含める。変更不要でも理由を明記して返信 |
| 言語を合わせる | 指摘者の言語(英語 / 日本語)で返信。OSS なので英語が多い |
| 全件取得 | スレッドが 100 件超なら pageInfo でページング |
ワークフロー
0. 未 resolve スレッドを取得
GraphQL を使う(REST は resolve 状態を返さない)。
PR_NUMBER="${1:-$(gh pr list --head "$(git branch --show-current)" --json number --jq '.[0].number')}"
REPO_INFO=$(gh repo view --json owner,name --jq '"\(.owner.login)|\(.name)"')
OWNER="${REPO_INFO%|*}"; REPO="${REPO_INFO#*|}"
gh api graphql -f query='
query($owner: String!, $repo: String!, $pr: Int!) {
repository(owner: $owner, name: $repo) {
pullRequest(number: $pr) {
reviewThreads(first: 100) {
pageInfo { hasNextPage endCursor }
nodes {
id isResolved path line
comments(first: 20) { nodes { databaseId body author { login } url } }
}
}
}
}
}
' -f owner="$OWNER" -f repo="$REPO" -F pr="$PR_NUMBER"1. 対応方針をユーザーに提示し、承認を得る(必須)
コード修正・返信の前に、各コメントを現在のコードで検証して表で提示する。
| # | ファイル | 指摘(要約) | 判定 | 対応方針 |
| 1 | path/to/file.rs:L42 | … | 要修正 / 対応不要 | 修正内容 or 不要と判断した理由 |
- 要修正: 指摘が正しく、コード修正が必要
- 対応不要: 現在のコードに該当しない(修正済み・削除済み)、または指摘が技術的に誤り
承認を得てから次へ進む。 ユーザーが方針を変えたらそれに従う。
2. 1 件ずつ修正 → コミット → push
cargo fmt --all
cargo clippy --all-targets --all-features -- -D warnings
cargo test --release --test <関連スイート>
git add <修正ファイル>
git commit -m "fix(<scope>): <要約>" # 英語の Conventional Commits
git push origin HEADpre-commit hook(cargo fmt && cargo clippy)を必ず通す。
3. スレッドに返信
gh api "repos/${OWNER}/${REPO}/pulls/${PR_NUMBER}/comments/${COMMENT_ID}/replies" -f body="返信内容"COMMENT_ID は GraphQL の databaseId。
4. ナレッジフィードバック(AI ボットの指摘のみ)
投稿者が coderabbitai[bot] / devin-ai-integration[bot] / chatgpt-codex-connector[bot] / claude[bot] 等の場合、対応後に実施する。
| 判定 | やること |
| 要修正だった | .claude/skills/*/SKILL.md(full-code-review, verify-svelte-compat, perf-loop など)と docs/ を横断検索。未記載なら最も近いスキルか docs/ に 1〜3 行で追記。記載済みなら記述が不明確でないか見直す |
| 対応不要だった | 「これは問題ない」文脈(公式 Svelte と意図的に異なる挙動、Rust 固有の最適化など)を該当スキルか compatibility/GATES.md の該当節に追記 |
CLAUDE.md(= AGENTS.md)は全セッションに読み込まれるため、追記は「短く・一般的で・実害があった規則」に限る(同ファイルの Maintaining This File 参照)。事例や数値は書かない。
追記・改善は ユーザーに確認してから 行い、結果を報告する。
返信テンプレート
修正した場合(英語):
Thanks for the catch!
[summary of the fix]
Fixed in: abc1234変更不要の場合(英語):
Thanks for the review!
[reasoning for keeping the current implementation]
- [reason 1]
- [link to spec / official Svelte source if relevant]
I'll keep the current implementation for the reasons above.日本語の指摘には同じ構成で「ご指摘ありがとうございます! … 対応コミット: abc1234」/「… 上記の理由から、現状の実装を維持させていただきます。」と返す。
公式 Svelte と意図的に挙動を変えている箇所は、その旨と根拠(例: CLAUDE.md → "Memory-efficient layout (u32 positions, compact_str)")を返信に明記する。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

