GROK BOT TOOLS · SKILL
Changelog entry check, findings only変更履歴と差分の照合(所見まで)
Compares an existing changelog entry with the diff, lists missing or overstated details, and stops before file edits, commits, pushes or tags.
既存の変更履歴を差分と照合し、抜けている説明や言い過ぎている記述を挙げます。ファイル編集・コミット・push・タグ作成の前で止まります。
Where it goesどこに貼るか
Grok Build: save the file as .grok/skills/changelog-entry-check/SKILL.md in the repository, or as ~/.grok/skills/changelog-entry-check/SKILL.md for every project. It then shows up as the slash command /changelog-entry-check.
Grok Build:リポジトリの .grok/skills/changelog-entry-check/SKILL.md に保存します。すべてのプロジェクトで使うなら ~/.grok/skills/changelog-entry-check/SKILL.md に。スラッシュコマンド /changelog-entry-check として呼べるようになります。
First three moves最初の3手
- Fill the blanks and save the text as ./.grok/skills/changelog-entry-check/SKILL.md in the repository.
- In Grok Build, invoke /changelog-entry-check with one entry and its local comparison range.
- Compare each reported omission or overstatement with the cited entry and code before applying corrections.
- 空欄を埋め、リポジトリ内の ./.grok/skills/changelog-entry-check/SKILL.md に保存します。
- Grok Build で /changelog-entry-check を呼び出し、変更履歴の1項目とローカルの比較範囲を指定します。
- 修正を適用する前に、指摘された説明の抜けや言い過ぎを、引用された記述とコードで確認します。
Where it stops止まる条件
- Before editing files, committing, pushing or tagging: it returns findings only.
- Before merging, deploying or any force operation.
- Before sending messages, publishing notes, purchasing, paying, deleting files or changing production.
- When the entry or comparison is missing or changes during review: affected findings remain unresolved.
- ファイル編集・コミット・push・タグ作成の前で止まり、所見だけを返します。
- マージ・デプロイ・強制操作の前で止まります。
- メッセージ送信・ノート公開・購入・支払い・ファイル削除・本番環境の変更の前で止まります。
- 対象の記述や比較材料がない場合、または確認中に変わった場合は、影響する所見を未解決とします。
Blanks to fill埋める空欄
| Blank空欄 | What goes there入れるもの |
|---|---|
[REPOSITORY] | Local repository containing the change and changelog.変更内容と変更履歴があるローカルリポジトリです。 |
[CHANGELOG_ENTRY] | Changelog file and exact section or entry to inspect.確認する変更履歴ファイルと、対象の節または項目です。 |
[BASE_REF] | Local reference used as the comparison base.比較元にするローカルの参照です。 |
[CHANGE_TARGET] | Local endpoint reference or supplied diff describing the change.変更後の状態を示すローカルの参照、または提示した差分です。 |
Replace every bracket. Leave none behind.
角かっこはすべて置き換え、残さないでください。
The text文面
Download SKILL.mdSKILL.md で持ち帰る Fork itフォークする Results & questions結果・質問を書く
--- name: changelog-entry-check description: Compare an existing changelog entry with a local diff and list omissions or overstated claims. Use when asked whether release wording matches the change. when-to-use: check this changelog entry, compare changelog with diff, find overstated release claims metadata: author: "BotShelf Vampire (unofficial, not xAI)" short-description: Changelog claims matched to changed behavior license: MIT --- # Changelog entry check, findings only ## When to use Use this when I ask whether an existing changelog entry describes a particular change accurately. Review the entry against the final diff, including any reversions. Keep all files unchanged. ## Inputs and access - Local repository: [REPOSITORY]. - Entry file and section: [CHANGELOG_ENTRY]. - Comparison base: [BASE_REF]. - Change endpoint or supplied diff: [CHANGE_TARGET]. Read local code, history, tests and release guidance. Do not fetch missing references or request secrets. ## Steps 1. Resolve the comparison and record its revisions or supplied diff identity. Locate the exact entry and note its heading, version and audience where stated. 2. Split the entry into factual claims. For each, find the changed code and enough surrounding behavior to explain what users can actually do after the change. 3. Match each claim to file and line evidence. Mark it supported, overstated, contradicted or unresolved. Flag wider availability, removed limitations or performance claims that the diff does not establish. 4. Work back from the diff to find omitted user effects. Check changed defaults, accepted inputs, error behavior and compatibility requirements. Exclude internal rearrangements unless they affect the stated audience. 5. Separate confirmed omissions from questions about intent. Suggest a narrow correction for each supported mismatch, retaining the entry's scope. Do not invent a release date, version or rollout status. ## Check the result Reconcile both directions: each entry claim has a status, and each relevant changed behavior has an entry reference or an omission reason. Recheck citations against the recorded revisions. Do not treat a test name or commit message alone as evidence of behavior. ## What to return Return the comparison identity, entry location, missing details and overstated claims. For each finding include the original wording, code evidence, user effect and proposed correction. Finish with unresolved questions and unread scope. Return the review in chat only. ## Needs my approval Stop before editing files, committing, pushing, tagging, merging, deploying or force operations. Stop before sending messages, publishing notes, purchasing, paying, deleting files or changing production. ## If data is missing or stale If the entry or comparison is unavailable, identify the gap and stop. If either changes during review, mark affected findings pending a fresh comparison. Do not reconstruct missing content 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 two-way check between changelog claims and changed behavior, with evidence for omissions and overstatements.
公式ページは 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棚を検索