Config Validator

To validate aeon.yml structural correctness in CI workflows, run the shared validator script to detect checkout ordering issues, duplicate keys, and missing skill definitions, reporting failures with remediation guidance.

Duplicate keys and missing skill definitions in aeon config files are caused by inconsistent CI configuration updates and conflicting inventory across PRs, which structural validation catches during PR validation and weekly audits.

Yes, the aeon config validator checks GitHub Actions workflow files by verifying structural correctness in .github/workflows/aeon.yml to prevent outages caused by misconfigurations like checkout step ordering issues.

To prevent outages caused by aeon.yml misconfigurations during PR validation, apply automated validation to catch missing skill definitions and verify that the CI configuration and skill registry remain consistent across PRs and main.

Yes, you can run automated config validation for weekly audits without external dependencies, as the validator operates using a standalone shared script to report problems and guide remediation for aeon.yml structural integrity.

The best way to catch checkout ordering issues in aeon workflows is to run automated structural validation during CI, which detects missing or conflicting inventory and ensures the skill registry remains consistent.