Stats
Actions
Tags
From data-engineering
Audits changes to dbt Semantic Layer definitions, flagging breaking changes and aggregation risks. Produces a report with blast radius, breaking changes, and recommendations.
How this command is triggered — by the user, by Claude, or both
Slash command
/data-engineering:semantic-change-check <changed_yml_files>The summary Claude sees in its command listing — used to decide when to auto-load this command
# 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 key...
.yml files defining metrics, semantic models, and dimensions.metrics:. If a calculation (expr) or aggregation type changed, flag it as a breaking change.semantic_models:. Ensure primary keys (entities) and dimensions are correctly mapped to the underlying SQL model.npx claudepluginhub yeaight7/agent-powerups --plugin data-engineering