config-drift-detector

To detect configuration drift, you compare a single source of truth against derived files. This Skill reads your SSOT from an iron-dome-limits.yaml reference and cross-checks values across pyproject.toml, Lefthook, .importlinter, and IDE settings to ensure consistency.

Configuration drift detection identifies divergences between a single source of truth and derived configuration files. You need it in automated pipelines and audits to prevent misconfigurations, non-compliance, and deployment issues across teams.

Yes, you can check pyproject.toml, Lefthook, .importlinter, and IDE settings against a central YAML source. The detector reads your SSOT from iron-dome-limits.yaml and compares corresponding values across these multiple sources.

No, the config drift detector does not modify any files. It generates a drift report detailing divergences and suggested remediations, ensuring safe audits without altering your actual configuration sources.

The best way to generate a drift report for SSOT-driven configurations is to run an automated detector that reads your central YAML source, compares it against derived files like .claude/rules/*.md, and outputs a detailed divergence report.