bug-check
CommandRun automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Audit changes to dbt Semantic Layer definitions for breaking changes and aggregation risks.
> /plugin marketplace add yeaight7/agent-powerups
description: "Audit changes to dbt Semantic Layer definitions for breaking changes and aggregation risks." argument-hint: "<changed_yml_files>"
1. **Protect Business Trust**: The semantic layer is the source of truth for the business. A silent change to a metric definition is worse than a broken pipeline. 2. **Review YML Only**: Focus your analysis on the `.yml` files defining metrics, semantic models, and dimensions.
1. Read the changed semantic layer files. 2. Identify modifications to `metrics:`. If a calculation (`expr`) or aggregation type changed, flag it as a breaking change. 3. Identify modifications to `semantic_models:`. Ensure primary keys (`entities`) and dimensions are correctly mapped to the underlying SQL model. 4. Check for removed metrics or dimensions. Flag these as critical breaking changes for downstream consumers. 5. Provide a concise report:
Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Use when a build, type check, or test suite is failing and needs to be unblocked with a minimal change.
Use when a bug needs systematic diagnosis before a fix is attempted.
Use to diagnose environment, tooling, and Agent Powerups setup problems.
Use to turn a spec or user request into working, tested code.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.