GROK BOT TOOLS · SKILL
Dependency update order, plan only依存関係の更新順序を計画する
Lists dependencies with evidence of newer versions, reads available changelogs, and orders proposed updates with risks. Stops at a plan; no installs or repository edits without approval.
新しいバージョンの根拠がある依存関係を挙げ、利用できる変更履歴を読んで、リスクを添えた更新順序を提案します。計画で止め、承認なしにインストールやリポジトリの編集はしません。
Where it goesどこに貼るか
Grok Build: save the file as .grok/skills/dependency-update-plan/SKILL.md in the repository, or as ~/.grok/skills/dependency-update-plan/SKILL.md for every project. It then shows up as the slash command /dependency-update-plan.
Grok Build:リポジトリの .grok/skills/dependency-update-plan/SKILL.md に保存します。すべてのプロジェクトで使うなら ~/.grok/skills/dependency-update-plan/SKILL.md に。スラッシュコマンド /dependency-update-plan として呼べるようになります。
First three moves最初の3手
- Fill the blanks and save the text as ./.grok/skills/dependency-update-plan/SKILL.md in the repository.
- Open the repository in Grok Build and invoke /dependency-update-plan for a small dependency scope.
- Read the version evidence, proposed order and unknowns before approving any installation or file change.
- 空欄を埋め、リポジトリ内の ./.grok/skills/dependency-update-plan/SKILL.md に文面を保存します。
- Grok Build でリポジトリを開き、少数の依存関係を対象に /dependency-update-plan を呼び出します。
- インストールやファイル変更を承認する前に、バージョンの根拠、更新順序、不明点を読みます。
Where it stops止まる条件
- Before installing dependencies or editing manifests, lockfiles or source: return a plan and ask for approval.
- Before committing, pushing, merging, deploying or using force operations: ask for approval.
- Before sending messages, publishing, purchasing, paying, deleting files or changing production: ask for approval.
- When version evidence or changelogs are missing or stale: mark the dependency unresolved instead of inventing a target.
- 依存関係のインストールや定義ファイル、ロックファイル、ソースの編集の前に、計画を返して承認を求めます。
- コミット、プッシュ、マージ、デプロイ、強制操作の前に、承認を求めます。
- メッセージの送信、公開、購入、支払い、ファイルの削除、本番環境の変更の前に、承認を求めます。
- バージョンの根拠や変更履歴がない、または古い場合は、更新先を作らず未解決と明記します。
Blanks to fill埋める空欄
| Blank空欄 | What goes there入れるもの |
|---|---|
[REPOSITORY] | Local repository whose dependency records should be read.依存関係の記録を読むローカルリポジトリです。 |
[DEPENDENCY_SCOPE] | Dependencies or repository components included in the plan.計画の対象とする依存関係やリポジトリ内の構成要素です。 |
[CHANGELOG_SOURCES] | Locally available or named changelogs and dated version records to consult.参照するローカルの変更履歴、または指定した変更履歴と日付付きのバージョン記録です。 |
[TARGET_POLICY] | Allowed version ranges, runtime constraints and update priorities.許容するバージョン範囲、実行環境の制約、更新の優先順位です。 |
Replace every bracket. Leave none behind.
角かっこはすべて置き換え、残さないでください。
The text文面
Download SKILL.mdSKILL.md で持ち帰る Fork itフォークする Results & questions結果・質問を書く
--- name: dependency-update-plan description: Read repository dependency records and available changelogs to propose an update order when asked to plan dependency maintenance. Return a plan without installing or changing files. when-to-use: plan dependency updates, review outdated dependencies, order dependency upgrades metadata: author: BotShelf Vampire (unofficial, not xAI) short-description: Dependency update order with evidence and risks license: MIT --- # Dependency update order, plan only ## When to use Use this when I ask for a dependency update plan. Keep all proposed changes in the response until I approve a separate implementation task. ## Inputs and access - Local repository: [REPOSITORY]. - Included dependencies or components: [DEPENDENCY_SCOPE]. - Changelogs and dated version records: [CHANGELOG_SOURCES]. - Version constraints and priorities: [TARGET_POLICY]. Read manifests, lockfiles, runtime requirements and relevant tests. Use available local or named source documents. Do not install tools or run commands that change dependency records to gather information. ## Steps 1. Record the repository revision and existing working changes. List the declared constraints and resolved versions separately; identify direct and indirect dependencies where the records allow it. 2. Compare these versions with the supplied version evidence. List outdated dependencies only where a newer version is supported by that evidence. Include the source date; do not call an undated version the latest. 3. Read the available changelogs between each current and proposed version. Note breaking changes, runtime requirements, related dependency constraints and migration work. Mark unread sections explicitly. 4. Propose an order based on prerequisites, compatibility and the stated priorities. Group changes only when they need to move together. Explain each dependency between steps. 5. For each step, give the proposed target, evidence, risks, focused checks and a way to restore the prior dependency state if implementation is later approved. Leave unsupported targets unresolved. ## Check the result Check that every proposed version fits the stated constraints or clearly names a conflict. Separate known changes from inferred risks. Confirm that no installation or repository edit was performed during planning. ## What to return Return an inventory, ordered update plan, source locations and dates, risk notes, suggested checks, and unresolved questions. Say which dependencies could not be assessed. ## Needs my approval Ask before installing anything or editing manifests, lockfiles or source. Stop before committing, pushing, merging, deploying or using force operations. Ask before sending messages, publishing, purchasing, paying, deleting files or changing production. ## If data is missing or stale Report missing records or inaccessible changelogs. If dates or repository versions disagree, identify the mismatch and make affected steps conditional. Do not guess release contents, freshness or compatibility 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 how Grok Build reads skill instructions. This text adds dependency evidence requirements, an update ordering method and a plan-only approval boundary.
公式ページは、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棚を検索