What problem does it solve?
Table or column name typos, unupdated references after schema renames, and infrastructure drift between source-of-truth schema definitions and deployed Azure Data Explorer clusters cause silent or 400-level KQL query failures that are time-consuming to debug.
Core Features & Use Cases
- Canonical Schema Cross-Check: Extracts table and column definitions from KQL setup scripts or Terraform-managed ADX resources, then scans application code for KQL queries to flag mismatched identifiers with exact file:line locations.
- Project-Wide Consistency Validation: Automatically searches for all occurrences of old schema names across the entire codebase after a migration to ensure no lingering references are missed.
- Optional Live Drift Detection: Compares the deployed ADX cluster schema against source-of-truth files to catch unplanned infrastructure changes that could break queries.
Use Case: After renaming a column in your ADX table during a schema migration, run this skill to scan all API route handlers and query helper functions to confirm no queries still reference the old column name.
Quick Start
Use the adx-schema-check skill to scan all KQL queries in the src/api directory for mismatches against the canonical ADX schema defined in scripts/adx-schema-setup.kql.