GROK BOT TOOLS · SKILL
PR review notes, no posted commentsPRのレビュー所見(投稿前まで)
Reviews a repository diff or branch for correctness risks, missing tests and unclear names. Returns findings with file and line, then stops before commits, pushes, merges or comment posting.
リポジトリの差分やブランチを読み、動作上のリスク、足りないテスト、分かりにくい名前を挙げます。ファイルと行番号を添えた所見を返し、コミット・push・マージ・コメント投稿の前で止まります。
Where it goesどこに貼るか
Grok Build: save the file as .grok/skills/pr-review-notes/SKILL.md in the repository, or as ~/.grok/skills/pr-review-notes/SKILL.md for every project. It then shows up as the slash command /pr-review-notes.
Grok Build:リポジトリの .grok/skills/pr-review-notes/SKILL.md に保存します。すべてのプロジェクトで使うなら ~/.grok/skills/pr-review-notes/SKILL.md に。スラッシュコマンド /pr-review-notes として呼べるようになります。
First three moves最初の3手
- Fill the blanks and save the text as ./.grok/skills/pr-review-notes/SKILL.md in the repository.
- In Grok Build, invoke /pr-review-notes for a small local diff or branch.
- Read each cited line and check the stated trigger and consequence before using the notes.
- 空欄を埋め、リポジトリ内の ./.grok/skills/pr-review-notes/SKILL.md に保存します。
- Grok Build で /pr-review-notes を呼び出し、ローカルの小さな差分やブランチを対象にします。
- 所見を使う前に、引用された行を読み、問題が起きる条件と影響を確かめます。
Where it stops止まる条件
- Before changing repository files, committing, pushing, merging or posting review comments.
- Before deployment or any force operation: it returns notes for review.
- Before sending messages, publishing, purchasing, paying, deleting or changing production.
- When the target or base is unclear or unavailable: it reports the gap instead of guessing.
- リポジトリ内のファイル変更、コミット、push、マージ、レビューコメントの投稿の前で止まります。
- デプロイや強制操作の前で止まり、確認用の所見を返します。
- メッセージの送信、公開、購入、支払い、削除、本番環境の変更の前で止まります。
- 対象や比較元が不明、または読めない場合は、推測せず不足を報告します。
Blanks to fill埋める空欄
| Blank空欄 | What goes there入れるもの |
|---|---|
[REPOSITORY] | Local repository to read.読む対象のローカルリポジトリです。 |
[REVIEW_TARGET] | Local branch, commit or supplied diff to review.確認するローカルブランチ、コミット、または提示した差分です。 |
[BASE_REF] | Local reference used as the comparison base.比較元にするローカルの参照です。 |
[REVIEW_FOCUS] | Behavior or area that deserves particular attention.特に注意して読む動作や範囲です。 |
Replace every bracket. Leave none behind.
角かっこはすべて置き換え、残さないでください。
The text文面
Download SKILL.mdSKILL.md で持ち帰る Fork itフォークする Results & questions結果・質問を書く
--- name: pr-review-notes description: Review a repository diff or branch and return notes with file and line references. Use when asked for a PR review, correctness review or missing test check. when-to-use: review this PR, review this diff, review this branch, find missing tests metadata: author: BotShelf Vampire (unofficial, not xAI) short-description: Repository review that stops at notes license: MIT --- # PR review notes, no posted comments ## When to use Use this when I ask for a review of a specific diff or branch. Read the change and its surrounding code before drawing conclusions. Keep the repository unchanged. ## Inputs and access - Local repository: [REPOSITORY]. - Review target: [REVIEW_TARGET]. - Comparison base: [BASE_REF]. - Particular focus: [REVIEW_FOCUS]. Use local files and history. Do not fetch remote changes or request credentials in chat. ## Steps 1. Read repository guidance, identify the target and base, and record their resolved revisions. Note existing working changes without replacing them. 2. Inspect the diff and the relevant callers, data flow and error handling. Follow changed behavior far enough to explain its effect. 3. Look for correctness risks and boundary cases. For each candidate, identify the input or condition that would cause the problem. 4. Read nearby tests. Describe missing coverage with a concrete case and expected behavior. Do not claim that absent coverage proves a defect. 5. Flag unclear names only when they obscure meaning or could lead to misuse. Keep these suggestions separate from correctness findings. 6. Rank findings by impact. Give the file, line, trigger, consequence and supporting evidence for each. Mark uncertain conclusions as questions. ## Check the result Check that each cited line belongs to the reviewed revision. Remove duplicate findings and unsupported claims. Distinguish observed code behavior from assumptions. Report the inspected scope and any areas left unread. ## What to return Return findings first, followed by missing tests, naming suggestions and open questions. If there are no supported findings, say so with the scope limits. Include a short list of checks that a person could run next. ## Needs my approval Stop before editing files, committing, pushing, merging, deploying, force operations or posting comments. Also stop before sending messages, publishing, purchasing, paying, deleting or changing production. Return notes only. ## If data is missing or stale If a reference is missing or the comparison is ambiguous, report it and stop. If the target changes during review, identify the mismatch and withhold conclusions about the new revision. Do not reconstruct missing code from memory.
License: MIT. Free, no sign-up. Use is at your own risk. BSV does not run it or set it up for you.
ライセンス:MIT。無料・登録不要。利用は自己責任です。BSVが代わりに実行・セットアップすることはありません。
What it adds to the official page公式ページに足しているもの
The official page describes the Grok Build skill format. This text adds a repository review sequence, evidence requirements for findings and a boundary before repository changes or comment posting.
公式ページは Grok Build のスキル形式を説明しています。この文面は、リポジトリを読む手順、所見に必要な根拠、リポジトリの変更やコメント投稿の前で止まる決まりを足しています。
Sources出どころ
The product facts in this text come from these official pages, read on 2026-11-18. Products change: when a page and this text disagree, the page is right.
この文面の製品に関する記述は、次の公式ページ(2026-11-18 に確認)に基づいています。製品は変わります。公式ページとこの文面が食い違うときは、公式ページが正です。
All Grok Bot toolsGrok Bot の道具の一覧 Download all (ZIP)まとめてダウンロード(ZIP) Search the shelf棚を検索