/semantic-change-check
Audit changes to dbt Semantic Layer definitions for breaking changes and aggregation risks.
$ npx -y skills add yeaight7/agent-powerups --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/semantic-change-check
Context preview
What this command does when you run it.
Audit changes to dbt Semantic Layer definitions for breaking changes and aggregation risks.
Command definition
semantic-change-check.mddescription: "Audit changes to dbt Semantic Layer definitions for breaking changes and aggregation risks." argument-hint: "<changed_yml_files>"
Semantic Change Check Command
CRITICAL BEHAVIORAL RULES
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.
Execution Steps
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:
- **Blast Radius**: (What dashboards/consumers are affected?)
- **Breaking Changes**: (List of broken metrics/dimensions)
- **Recommendations**: (e.g., "Version the metric instead of modifying it in place.")
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
Repo: yeaight7/agent-powerups
Other commands on agent-powerups.
- /bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Open command - /build-fix
Use when a build, type check, or test suite is failing and needs to be unblocked with a minimal change.
Open command - /debug
Use when a bug needs systematic diagnosis before a fix is attempted.
Open command - /doctor
Use to diagnose environment, tooling, and Agent Powerups setup problems.
Open command - /implement
Use to turn a spec or user request into working, tested code.
Open command - /mcp-check
Use to check MCP server prerequisites before activating or using a server.
Open command

