メニュー
Read a live Postgres schema — tables, columns, types, primary keys, indexes, and the foreign-key graph — into a normalized snapshot for planning and debugging. Read-only. Use before changing data access, writing a migration, or reasoning about how tables relate.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run EXPLAIN [ANALYZE] on a query and return the parsed plan with flags for sequential scans and probable missing indexes — performance evidence, not a guess. Read-only. Use when a query is slow or before shipping a query-heavy path.
Detect schema drift between SQLAlchemy models and the live Postgres — missing/extra columns, nullability mismatches, type mismatches. Reflects the models via a Python sidecar and diffs in TS. Read-only. Use as a pre-ship gate or when "the code says one thing, the DB says another".
Assert live database state as verify-phase evidence. Run a read-only query and check it against an expected exists / row_count / value, returning a structured PASS/FAIL — not raw rows. Use to prove a row exists, a count matches, or a value landed after a change.
Mutate data behind a transaction guard — preview a statement inside a held transaction (no commit), inspect the impact, then confirm to COMMIT or rollback to discard. The only dblab skill that writes. Use for any INSERT/UPDATE/DELETE that must be safe and reviewable.
| name | db-introspect |
| description | Read a live Postgres schema — tables, columns, types, primary keys, indexes, and the foreign-key graph — into a normalized snapshot for planning and debugging. Read-only. Use before changing data access, writing a migration, or reasoning about how tables relate. |
Single-backend skill. Calls rolepod_db_introspect on the rolepod-dblab MCP server and surfaces the structured result. No fallback (D-001).
What does the live schema actually look like — tables, columns, types, indexes, foreign keys?
Phase: Plan / Debug. Read-only.
rolepod-wplab (/wp-introspect), not dblab. wplab understands WP-semantic structure (options, post meta, taxonomies); db-introspect returns raw tables/columns/FKs with no WP meaning. (No-overlap contract, SPEC §3.)wpdb semantics → rolepod-wplab.conn — Postgres connection string (postgresql://…). Treated as a secret; never logged.schema (optional, default public) — schema to introspect.include_row_counts (optional, default false) — add estimated row counts (pg_class.reltuples; cheap, not exact).Call rolepod_db_introspect:
{
"conn": "postgresql://user:pass@host:5432/db",
"schema": "public",
"include_row_counts": false
}
table_count — number of base tables in the schema.tables[] — each: name, columns[] (name, type, nullable, default, primaryKey), indexes[] (name, columns, unique), foreignKeys[] (name, columns, refTable, refColumns), rowCount.manifest_path — Extension Protocol v1 manifest (phase debug).User: "What does the orders schema look like before I touch it?"
{ "conn": "postgresql://…/shop", "schema": "public", "include_row_counts": true }
Surface the FK graph and indexes; flag any table the migration will touch.
Run artifacts are saved under:
.rolepod-dblab/artifacts/db-introspect_<ts>_<uuid>/rolepod parent (detected via the marker file <git-root>/.rolepod/parent-active written by the parent's SessionStart hook): <git-root>/.rolepod/evidence/<ts>-rolepod-dblab-db-introspect/Either way the run directory contains schema.json plus a manifest.json per Extension Protocol v1, so the parent's check-work / debug-issue skills can read the live schema as evidence.
The
/db-introspectskill needs the rolepod-dblab MCP server, which is not currently available. Confirm the plugin is installed and try again, or check thatnpx -y @rolepod/dblabis reachable.