メニュー
Run and verify SeaORM database migrations against in-memory SQLite. Use when applying migrations, verifying schema changes, or testing migration correctness.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | migration-runner |
| description | Run and verify SeaORM database migrations against in-memory SQLite. Use when applying migrations, verifying schema changes, or testing migration correctness. |
Run and verify SeaORM database migrations for LibrAgent.
use sqlx::sqlite::SqlitePoolOptions;
use sea_orm::SqlxSqliteConnector;
use tauri_mcp_agent_lib::migration::Migrator;
use sea_orm_migration::MigratorTrait;
async fn setup_db() -> sea_orm::DatabaseConnection {
let pool = SqlitePoolOptions::new()
.connect("sqlite::memory:")
.await
.unwrap();
let db = SqlxSqliteConnector::from_sqlx_sqlite_pool(pool);
Migrator::up(&db, None).await.unwrap();
db
}
let db = setup_db().await;
// Verify tables exist
let result = db.query_all(
"SELECT name FROM sqlite_master WHERE type='table'"
).await.unwrap();
assert!(result.iter().any(|r| r["name"].to_string().contains("expected_table")));
let db = setup_db().await;
Migrator::up(&db, None).await.unwrap();
// Verify schema after up
Migrator::down(&db, None).await.unwrap();
// Verify schema after down
let db = setup_db().await;
// Attempt invalid foreign key insertion
// Verify foreign key constraint is enforced
src-tauri/src/migration/ - Migration filessrc-tauri/src/repositories/ - Repository implementationsscripts/verify_phase2_migration.sh - Legacy migration verificationscripts/test_planning_module.sh - Legacy module testingTests must be in src-tauri/tests/ as integration tests. Run with:
cargo test --tests
Analyze installed tools and existing assistant configurations to actively propose and create specialized LibrAgent assistants via agent__create. Use when the user wants to recruit, create, or build a domain expert or specialist agent, utilizing a proactive "Architect" workflow that maps available inventory tools to functional gaps. Not for workspace agents.md (agent-init), teamwork/org, or registering MCP servers.
Parse .trace.json files and correlate with backend events and tool calls. Use when debugging agent behavior, investigating tool call patterns, or validating concurrency limits.
Monitor and enforce the frontend bundle size budget. Use when checking bundle size, preventing regressions, or validating build output against budget constraints.
Audit React Context usage, detect prop drilling, verify compound component patterns. Use when reviewing frontend code for proper Context consumption, checking AgentChatContext/AgentSessionContext usage, or enforcing compound component patterns.
Audit builtin MCP tool implementations against the Tool Design Manifesto. Use when reviewing builtin tools for compliance, checking context_prompt usage, validating text-first MCPResult design, or auditing canonical naming and session isolation correctness.
Scaffold integration tests in src-tauri/tests/ following the project's strict rules. Use when creating new Rust tests, ensuring CI compatibility, or preventing false sense of test coverage from unit tests in src/.