メニュー
Trace upstream or downstream dependencies for a dbt resource. Use for lineage, build order, or downstream blast radius.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | trace-dependencies |
| description | Trace upstream or downstream dependencies for a dbt resource. Use for lineage, build order, or downstream blast radius. |
| compatibility | dbt-tools on PATH; unique_id required. |
Handle: dbt-tools-cli:trace-dependencies
unique_id; direction (upstream or downstream, CLI default downstream); optional depth; optional build order (upstream)bind-targetcheck-session — manifest presentunique_id from find-resources when unknowndescribe-resource)Reload in-memory artifacts after dbt run or a known artifact change. Use on the same target without restarting MCP.
Establish the dbt artifact root for this session (local path, s3://, or gs://). Use before any other dbt-tools analysis primitive.
Check MCP session state—target, load time, stale flag, runs, warehouse type. Use as a gate before analysis primitives.
Establish the dbt artifact root for this session (local path, s3://, or gs://). Use before any other dbt-tools analysis primitive.
Check whether dbt artifacts exist, are fresh, and which readiness level applies. Use as a gate before manifest- or run_results-based analysis.
Return metadata and context for one dbt resource by unique_id. Use when explaining what a model, source, or test does.