adx-schema-check

Validate KQL query identifiers against canonical ADX schema definitions.

1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/sergeyitaly/claude-skill-deployer --skill adx-schema-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adx-schema-check
Source: https://github.com/sergeyitaly/claude-skill-deployer/tree/main/skills_library/adx-schema-check
Command: npx skills add https://github.com/sergeyitaly/claude-skill-deployer --skill adx-schema-check

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about adx-schema-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent KQL query failures caused by ADX schema mismatches?

Prevent KQL query failures by cross-checking table and column identifiers in application code against canonical Azure Data Explorer schema definitions, flagging mismatches with exact file and line locations before runtime execution.

How do I validate KQL queries after renaming a column in an Azure Data Explorer table?

Validate KQL queries after a schema migration by scanning the entire codebase for lingering references to old table or column names, ensuring all application code matches the updated ADX schema definitions.

What is the best way to detect infrastructure drift between Terraform-managed ADX clusters and source schema files?

Detect infrastructure drift by comparing the deployed Azure Data Explorer cluster schema against source-of-truth configuration files, catching unplanned changes that could break KQL queries.

Does adx-schema-check work with KQL setup scripts to verify project-wide schema consistency?

Yes, it extracts table and column definitions from KQL setup scripts or Terraform-managed ADX resources, then scans application code to verify project-wide schema consistency and prevent 400-level query failures.

Why do my Azure Data Explorer API queries return 400-level errors after a schema update?

Azure Data Explorer API queries return 400-level errors when application code contains table or column name typos or unupdated references after schema renames, which can be identified by validating query identifiers against canonical schema files.

Can I find exact file and line locations of outdated KQL query identifiers in my codebase?

Yes, you can find exact file and line locations of outdated KQL query identifiers by scanning application code against canonical ADX schema definitions to flag mismatched table and column names.