GROK BOT TOOLS · SKILL
Migration plan review, no database executionデータベース移行計画の確認(実行なし)
Reviews a migration file for locking, backfill size, code rollout order and recovery options. Returns risks and open questions, then stops before file changes; it never runs a migration against any database.
移行ファイルを読み、ロック、データ補完の規模、コードの適用順序、復旧方法を確認します。リスクと未解決の点を返し、ファイル変更の前で止まります。どのデータベースに対しても移行を実行しません。
Where it goesどこに貼るか
Grok Build: save the file as .grok/skills/migration-plan-review/SKILL.md in the repository, or as ~/.grok/skills/migration-plan-review/SKILL.md for every project. It then shows up as the slash command /migration-plan-review.
Grok Build:リポジトリの .grok/skills/migration-plan-review/SKILL.md に保存します。すべてのプロジェクトで使うなら ~/.grok/skills/migration-plan-review/SKILL.md に。スラッシュコマンド /migration-plan-review として呼べるようになります。
First three moves最初の3手
- Fill the blanks and save the text as ./.grok/skills/migration-plan-review/SKILL.md in the repository.
- In Grok Build, invoke /migration-plan-review with one migration file and its related local code change.
- Compare the operation risks and rollout order with the cited files, and supply missing engine or data size details before acting.
- 空欄を埋め、リポジトリ内の ./.grok/skills/migration-plan-review/SKILL.md に保存します。
- Grok Build で /migration-plan-review を呼び出し、移行ファイル1つと関連するローカルのコード変更を指定します。
- 操作ごとのリスクと適用順序を引用元のファイルと見比べ、実施前にデータベースの種類・バージョンやデータ量の不足情報を補います。
Where it stops止まる条件
- Never executes a migration against any database, including a local or disposable database.
- Before changing files, committing, pushing, merging, deploying or force operations: it asks for approval.
- Before sending messages, publishing, purchasing, paying, deleting or changing production.
- When engine details or data size are unknown: it leaves dependent risk judgments open.
- When migration or code revisions change during review: it marks affected conclusions as stale.
- ローカルや使い捨ての環境を含め、どのデータベースに対しても移行を実行しません。
- ファイル変更、コミット、push、マージ、デプロイ、強制操作の前に承認を求めます。
- メッセージ送信、公開、購入、支払い、削除、本番環境の変更の前で止まります。
- データベースの種類・バージョンやデータ量が不明な場合は、それらに依存するリスクの判断を保留します。
- 確認中に移行ファイルやコードの版が変わった場合は、影響する所見が古くなったことを示します。
Blanks to fill埋める空欄
| Blank空欄 | What goes there入れるもの |
|---|---|
[REPOSITORY] | Local repository containing the migration and application code.移行ファイルとアプリケーションのコードがあるローカルリポジトリを指定します。 |
[MIGRATION_FILE] | Migration file to inspect without executing it.実行せずに内容を確認する移行ファイルを指定します。 |
[CODE_CHANGE] | Related local code diff or revision range, including its base.関連するローカルのコード差分、または比較元を含む版の範囲を指定します。 |
[ENGINE_DETAILS] | Database engine, version and supplied notes about relevant operation behavior.データベースの種類・バージョンと、対象操作の動作について参照できる資料を指定します。 |
[DATA_PROFILE] | Dated table size estimates, write activity and any supplied backfill limits; mark unknowns.日付付きのテーブル規模の見積もり、書き込み状況、データ補完の制約を指定し、不明な点はその旨を記します。 |
Replace every bracket. Leave none behind.
角かっこはすべて置き換え、残さないでください。
The text文面
Download SKILL.mdSKILL.md で持ち帰る Fork itフォークする Results & questions結果・質問を書く
--- name: migration-plan-review description: Review a repository migration file for locking, backfill scope, rollout order and recovery options. Use when asked to assess a database change before execution. when-to-use: review this migration, assess migration order, check backfill risks, inspect migration recovery metadata: author: "BotShelf Vampire (unofficial, not xAI)" short-description: Migration review without database execution license: MIT --- # Migration plan review, no database execution ## When to use Use this when I ask for a review of a proposed database migration and its related application change. Read files only; never execute the migration against any database, including local or disposable databases. ## Inputs and access - Repository: [REPOSITORY]. - Migration file: [MIGRATION_FILE]. - Related diff and comparison base: [CODE_CHANGE]. - Engine, version and supplied behavior notes: [ENGINE_DETAILS]. - Dated size estimates and write activity: [DATA_PROFILE]. Use local sources. Do not connect to a database or request credentials. ## Steps 1. Read repository guidance and record the migration revision and code comparison. List schema operations and data updates in their written order. 2. For each operation, identify affected tables, indexes and constraints. Use supplied engine details to discuss possible locks, scans or rewrites. Separate supported behavior from questions that need an engine specialist. 3. Inspect backfill predicates, batching, transaction scope, progress tracking and restart behavior. Relate the affected data estimate to the proposed batch size. Do not invent row counts or completion times. 4. Trace old and new application reads and writes. Describe which schema each version expects and whether both can coexist during rollout. Flag removals or constraints that require a preceding code or data change. 5. Read the reversal steps. Distinguish restoring a schema from restoring lost data. List assumptions about backups, retained columns or a forward repair, and mark any irreversible operation. 6. Order the concerns by impact and attach file and line evidence. Propose review questions and sequence changes without editing files. ## Check the result Account for every migration operation. Ensure each recovery suggestion addresses both schema and data. A reversal script alone is not evidence that recovery will succeed. ## What to return Return an operation risk table, backfill questions, proposed rollout order and recovery limits. Include source revisions, unknowns and any unread scope. ## Needs my approval Ask before editing files, committing, pushing, merging, deploying or force operations. Stop before sending, publishing, purchasing, paying, deleting or changing production. This review never runs migrations or database commands. ## If data is missing or stale Missing engine details or data estimates leave dependent conclusions open. If a source revision changes, mark affected findings stale and request the current files. Return completed observations separately from unresolved questions.
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 migration operation inventory, rollout ordering checks and recovery questions without database execution.
公式ページは 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棚を検索