metric-impact-analyzerlisted

# Metric Impact Analyzer Use this skill when a change may affect metrics, semantic models, dashboards, reporting, or stakeholder-facing KPIs. ## Goals - Detect whether a technical change also changes business meaning. - Identify likely downstream breakage in BI tooling and dashboards. - Separate harmless refactors from definition-level changes. ## What to Inspect - Metric definitions and calculation logic. - Semantic model changes (dimensions, measures, relationships). - Renamed or removed fields referenced by saved queries or dashboards. - Changed filters, time windows, or default values. - Changed joins, granularity, or fanout. - Contract-breaking field type changes (e.g., INT → FLOAT, nullable → NOT NULL). ## Change Classification | Change type | Risk level | Action required | |---|---|---| | Column rename with alias preserved | Low | Validate alias propagation | | Description or label change | Low | Confirm no tooling parses descriptions | | New optional field added | Low | No action unless it changes defaults | | Filter condition tightened | Medium | Validate that the new filter matches intent | | Metric formula changed | High | Stakeholder review required | | Grain changed (e.g., day → week) | High | All downstream rollups must be revalidated | | Dimension removed | Breaking | Cannot ship without migration plan | | Join path changed | Breaking | All dependent metrics may be affected | ## Analysis Steps 1. Summarize what changed technically (field names, types, lo