メニュー
Scaffold and apply a sqlx database migration the OpenWorkspace way, then refresh the offline query cache. Use when adding or changing the PostgreSQL schema in crates/db.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | new-migration |
| description | Scaffold and apply a sqlx database migration the OpenWorkspace way, then refresh the offline query cache. Use when adding or changing the PostgreSQL schema in crates/db. |
| argument-hint | <migration_name> |
| allowed-tools | Bash(sqlx *) Bash(cargo sqlx *) Bash(git add *) |
Add a reversible sqlx migration under crates/db/migrations and keep the offline cache in sync. Requires DATABASE_URL set (it's in .claude/settings.local.json) and the dev database up (podman compose -f deploy/dev/compose.yaml up -d).
sqlx migrate add -r <name> --source crates/db/migrations*.up.sql and *.down.sql. Keep the down migration a true inverse. Follow the schema conventions already in crates/db/migrations and the data model in docs/ — read the relevant phase spec before designing tables; do not infer the schema.sqlx migrate run --source crates/db/migrations (revert with sqlx migrate revert --source crates/db/migrations).query!/query_as! call or the schema they touch, regenerate the offline cache and commit it:
cargo sqlx prepare --workspace.sqlx/ together (git add crates/db/migrations .sqlx). CI runs cargo sqlx prepare --workspace --check and fails if .sqlx/ is stale.Then build/test to confirm the new queries compile against the schema.
Stage and commit the current changes as a single Conventional Commit that passes this repo's commit-msg rules. Use when the user asks to commit work in OpenWorkspace.
Scaffold a new workspace crate or app the OpenWorkspace way — edition 2024, inherited lints, thiserror error type, thin facade lib.rs. Use when adding a new member under crates/ or apps/.
Run the full OpenWorkspace quality gate and report pass/fail per check before opening or updating a PR. Use when the user wants to verify a branch is green, or is about to push or open a PR.
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros, closures, observability, testing, and common anti-patterns. Invoke with /rust-skills.