GROK BOT TOOLS · SKILL
README command check, proposed edits onlyREADMEのコマンド確認(修正案まで)
Checks README commands, paths and task names against repository definitions. Returns proposed edits and stops before executing commands, editing files, committing or pushing.
READMEのコマンド・パス・タスク名をリポジトリ内の定義と照合します。修正案を返し、コマンド実行・ファイル編集・コミット・pushの前で止まります。
Where it goesどこに貼るか
Grok Build: save the file as .grok/skills/readme-command-check/SKILL.md in the repository, or as ~/.grok/skills/readme-command-check/SKILL.md for every project. It then shows up as the slash command /readme-command-check.
Grok Build:リポジトリの .grok/skills/readme-command-check/SKILL.md に保存します。すべてのプロジェクトで使うなら ~/.grok/skills/readme-command-check/SKILL.md に。スラッシュコマンド /readme-command-check として呼べるようになります。
First three moves最初の3手
- Fill the blanks and save the text as ./.grok/skills/readme-command-check/SKILL.md in the repository.
- In Grok Build, invoke /readme-command-check for one README section and a named environment.
- Read each proposed edit beside its README line and repository definition before changing the document.
- 空欄を埋め、リポジトリ内の ./.grok/skills/readme-command-check/SKILL.md に保存します。
- Grok Build で /readme-command-check を呼び出し、READMEの1節と想定する環境を指定します。
- 文書を変更する前に、各修正案をREADMEの該当行とリポジトリ内の定義に照らして確認します。
Where it stops止まる条件
- Before executing documented commands or installing dependencies: this is a static review.
- Before editing files, committing, pushing, merging, deploying or any force operation.
- Before sending messages, publishing documentation, purchasing, paying, deleting files or changing production.
- When definitions are missing or changed: it marks the affected instructions unresolved instead of guessing a command.
- 記載されたコマンドの実行や依存関係のインストールの前で止まり、ファイルを読む範囲で確認します。
- ファイル編集・コミット・push・マージ・デプロイ・強制操作の前で止まります。
- メッセージ送信・文書公開・購入・支払い・ファイル削除・本番環境の変更の前で止まります。
- 定義がない場合や変わった場合は、コマンドを推測せず、影響する説明を未解決とします。
Blanks to fill埋める空欄
| Blank空欄 | What goes there入れるもの |
|---|---|
[REPOSITORY] | Local repository whose files and task definitions should match the README.READMEと照合するファイルやタスク定義があるローカルリポジトリです。 |
[README_FILE] | Repository path to the README to inspect.確認するREADMEのリポジトリ内のパスです。 |
[SECTIONS] | README sections whose commands and paths should be checked.コマンドとパスを確認するREADMEの節です。 |
[ENVIRONMENT] | Intended shell and operating system for the instructions.説明が想定するシェルとOSです。 |
Replace every bracket. Leave none behind.
角かっこはすべて置き換え、残さないでください。
The text文面
Download SKILL.mdSKILL.md で持ち帰る Fork itフォークする Results & questions結果・質問を書く
--- name: readme-command-check description: Compare README commands and paths with local repository definitions and propose corrections. Use when asked to check setup or task instructions against the codebase. when-to-use: check README commands, check documented paths, compare README tasks with scripts metadata: author: "BotShelf Vampire (unofficial, not xAI)" short-description: README command and path corrections as a list license: MIT --- # README command check, proposed edits only ## When to use Use this when I ask whether README commands and paths match the repository. Check what each instruction refers to and propose specific edits. Do not execute the documented commands during this review. ## Inputs and access - Local repository: [REPOSITORY]. - README file: [README_FILE]. - Sections to inspect: [SECTIONS]. - Intended shell and operating system: [ENVIRONMENT]. Use read access to documentation, script definitions, task configuration and files. Keep the working tree unchanged and use no network sources. ## Steps 1. Read repository guidance and record the current revision and relevant working changes. Extract commands and paths from the named sections, preserving their line numbers and stated prerequisites. 2. Track the working directory through each sequence. Distinguish literal paths from example values, generated outputs and files that should already exist. Check path spelling and case against the repository. 3. Resolve each named script or task to its definition. Inspect referenced entry files and arguments. Follow local wrappers far enough to identify the underlying task without running them. 4. Compare command order with required setup steps. Flag undefined tasks, missing entry files, misplaced directory changes and options unsupported by the inspected definitions. Treat shell or environment differences as conditional findings. 5. For each supported mismatch, propose the smallest wording or command correction and cite its repository evidence. When intent is unclear, supply a question instead of inventing a replacement command. ## Check the result Each proposal must identify a README line and the corresponding definition or bounded file search. Do not mistake a generated path's current absence for an error. Distinguish a command that names an existing task from one known to work at runtime; static inspection establishes only the former. ## What to return Return a list of proposed edits with the original instruction, reason, evidence location and replacement text. Follow it with unresolved commands, environment assumptions and sections not inspected. Report when no supported correction was found within the stated scope. ## Needs my approval Stop before editing files, running project commands, installing dependencies, committing, pushing, merging, deploying or force operations. Stop before sending messages, publishing documentation, purchasing, paying, deleting files or changing production. ## If data is missing or stale Report missing definitions or unreadable files as unresolved. If the README or relevant definitions change during review, identify affected proposals and withhold them until compared again. Do not guess 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 command-to-definition tracing, working-directory checks and a proposed-edit list that separates static evidence from runtime questions.
公式ページは 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棚を検索