Pipeline Incident Commander
When a pipeline fails, the Commander spawns parallel sub-agents to read logs, profile the warehouse, and notify owners — then posts a structured incident report with a proposed fix to Slack.
#1 on dbt Labs' ADE Workbench · 94% AI acceptance rate · 10X engineering velocity
MCP
Paradime MCP
Kiro
Claude
Cursor
OpenCode
Github
CoCo
Available tools
Once connected, your client has access to all tools below.
Start with seven production-ready reference agents from Paradime. Fork them, customize the prompt and toolset, then publish your version to your team's catalog.
When a pipeline fails, the Commander spawns parallel sub-agents to read logs, profile the warehouse, and notify owners — then posts a structured incident report with a proposed fix to Slack.
Auto-retries with smart backoff, isolates the failing model, generates a targeted fix in an isolated sandbox, and re-runs only what's downstream. Closes the loop with a PR for review.
Hunts idle warehouses, unclustered tables, and runaway queries. Files a weekly PR with commits that compound — typically 20–40% off the Snowflake bill in the first quarter.
Generates column-level descriptions, model docs, and lineage notes grounded in real query patterns. Bi-directional sync keeps your yaml, Confluence pages, and data catalog aligned.
Audits your dbt™ project for missing tests, infers what each model actually needs from its lineage and column types, and proposes the tests in a PR — no busywork, no boilerplate.
Reviews every dbt™ pull request for SQL anti-patterns, breaking schema changes, missing tests, and lineage impact. Posts inline comments and approves only when the model is production-ready.