菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | db-explain |
| description | 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. |
Single-backend skill. Calls rolepod_db_explain on the rolepod-dblab MCP server and surfaces the structured result. No fallback (D-001).
Is this query going to scan a whole table? Where is an index missing?
Phase: Perf / Review. Read-only — EXPLAIN runs inside a READ ONLY transaction, so even ANALYZE (which executes the query) cannot mutate.
rolepod-wplab for WP query concerns./db-query. You want to mutate → /db-write.conn — connection string (secret; never logged).sql — the query to analyze.analyze (optional, default false) — use EXPLAIN ANALYZE (executes the query to get real timings; still read-only).Call rolepod_db_explain:
{ "conn": "postgresql://…/db", "sql": "SELECT * FROM events WHERE kind = 'a'", "analyze": false }
has_concerns — true if any probable-missing-index flag fired.flags[] — each: kind (seq_scan | possible_missing_index), relation, plan_rows, filter?, detail.plan — the raw parsed JSON plan; manifest_path (phase review, status warn when concerns, else pass).{ "conn": "postgresql://…/db", "sql": "SELECT * FROM events WHERE kind = 'signup'" }
A possible_missing_index flag on events with the filter on kind → consider CREATE INDEX … ON events(kind).
.rolepod-dblab/artifacts/db-explain_<ts>_<uuid>/rolepod parent (marker <git-root>/.rolepod/parent-active): <git-root>/.rolepod/evidence/<ts>-rolepod-dblab-db-explain/The run directory holds plan.json + a manifest.json (Extension Protocol v1), so review-code can read the plan as performance evidence.
The
/db-explainskill 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.
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.
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.