GROK BOT TOOLS · SKILL
Changed paths and the tests they still need変更された処理経路と不足するテストの一覧
Maps changed code paths to existing tests, lists gaps with search evidence, and proposes one first test per gap. Stops before writing files, committing or pushing.
変更された処理経路と既存テストを照合し、調べた範囲を添えて不足を挙げます。各不足について最初に書くテストを1件提案し、ファイルの書き込み・コミット・pushの前で止まります。
Where it goesどこに貼るか
Grok Build: save the file as .grok/skills/test-gap-list/SKILL.md in the repository, or as ~/.grok/skills/test-gap-list/SKILL.md for every project. It then shows up as the slash command /test-gap-list.
Grok Build:リポジトリの .grok/skills/test-gap-list/SKILL.md に保存します。すべてのプロジェクトで使うなら ~/.grok/skills/test-gap-list/SKILL.md に。スラッシュコマンド /test-gap-list として呼べるようになります。
First three moves最初の3手
- Fill the blanks and save the text as ./.grok/skills/test-gap-list/SKILL.md in the repository.
- In Grok Build, invoke /test-gap-list on a small local diff with the named test scope.
- Compare the path map and proposed test inputs with the cited tests before approving any file writes.
- 空欄を埋め、リポジトリ内の ./.grok/skills/test-gap-list/SKILL.md に保存します。
- Grok Build で /test-gap-list を呼び出し、小さなローカル差分と指定したテスト範囲を対象にします。
- ファイルの書き込みを承認する前に、処理経路の対応表と提案されたテスト入力を、参照先のテストと照合します。
Where it stops止まる条件
- Before writing source, tests or reports to files: return the gap list for approval.
- Before running tests or collecting new coverage: use existing local evidence for this review.
- Before committing, pushing, merging, deploying, force operations or opening a pull request.
- Before sending messages, publishing, purchasing, paying, deleting or changing production.
- When revisions, test scope or coverage evidence disagree: report the uncertainty instead of claiming a path is untested.
- ソース・テスト・報告をファイルに書く前で止まり、不足の一覧を承認用に返します。
- テストの実行やカバレッジの新規計測はせず、この確認では既存のローカル資料を使います。
- コミット・push・マージ・デプロイ・強制操作・プルリクエスト作成の前で止まります。
- メッセージの送信・公開・購入・支払い・削除・本番環境の変更の前で止まります。
- リビジョン・テストの範囲・カバレッジ資料が食い違う場合は、未テストと断定せず不確かな点を報告します。
Blanks to fill埋める空欄
| Blank空欄 | What goes there入れるもの |
|---|---|
[REPOSITORY] | Local repository containing the diff and tests.差分とテストがあるローカルリポジトリを指定します。 |
[BASE_REF] | Local revision before the changes.変更前のローカルリビジョンを指定します。 |
[TARGET_REF] | Local revision whose changed paths need review.変更された処理経路を調べるローカルリビジョンを指定します。 |
[TEST_SCOPE] | Test directories, suites and configuration to inspect.確認するテストのディレクトリ・スイート・設定を指定します。 |
[COVERAGE_EVIDENCE] | Existing local coverage report with revision and run scope, or none.リビジョンと実行範囲が分かる既存のローカルカバレッジ報告を指定します。なければ none と記入します。 |
Replace every bracket. Leave none behind.
角かっこはすべて置き換え、残さないでください。
The text文面
Download SKILL.mdSKILL.md で持ち帰る Fork itフォークする Results & questions結果・質問を書く
--- name: test-gap-list description: Map changed repository code paths to existing tests and propose one test for each supported gap. Use when asked which tests a diff still needs. when-to-use: list test gaps, find untested changed paths, suggest tests for this diff metadata: author: "BotShelf Vampire (unofficial, not xAI)" short-description: Changed paths with evidence and first test cases license: MIT --- # Changed paths and the tests they still need ## When to use Use this when I ask which changed paths need tests. Focus on missing execution paths and assertions, rather than a general code review. ## Inputs and access - Local repository: [REPOSITORY]. - Comparison base: [BASE_REF]. - Target revision: [TARGET_REF]. - Test directories and suites: [TEST_SCOPE]. - Existing coverage report, or none: [COVERAGE_EVIDENCE]. Read local source, tests, fixtures and configuration only. Do not run tests, generate coverage or fetch remote files. ## Steps 1. Read repository guidance, resolve the revisions and record the diff scope. Leave existing working changes untouched. 2. Map changed branches, error paths, boundary inputs and state transitions. Give each path a condition, expected observable outcome and source location. Group paths only when one test can distinguish their behavior. 3. Follow test callers, shared fixtures and parameterized cases. Check suite selection and skipped cases. Record directories and symbols searched; a missing direct reference does not establish that no test reaches a path. 4. Match any supplied coverage report to its revision and run scope. Label an unexercised path as such only within that report's scope. Otherwise say "no matching test found" or "execution unknown." Treat missing assertions separately from missing execution. 5. For each supported gap, propose one test name, likely test file, setup, input and assertion. Explain what regression it would catch. Rank cases by consequence and how well each distinguishes the changed behavior; do not invent a defect to justify a test. ## Check the result Recheck each gap against indirect and parameterized tests. Cite evidence for expected behavior. Remove duplicates and paths outside the diff. Do not equate line coverage with a meaningful assertion. ## What to return Return resolved revisions, a path map and prioritized gaps. For each gap include evidence, search scope, uncertainty and the first proposed test. List unread suites and unavailable reports. Return recommendations in the response only. ## Needs my approval Ask before writing any files, running tests, committing, pushing, merging, deploying, force operations or opening a pull request. Stop before sending messages, publishing, purchasing, paying, deleting or changing production. ## If data is missing or stale Stop if either revision is unavailable. Discard stale coverage as execution evidence and continue source inspection with explicit limits. Report partial coverage of the review; never infer a passing suite or complete test coverage from missing data.
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 changed path map, evidence labels for test gaps and one proposed test case per gap.
公式ページは Grok Build のスキル形式を説明しています。この文面は、変更された処理経路の対応表、テスト不足の根拠の区分、不足ごとに1件のテスト案を加えています。
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棚を検索