validate-quality-config

To check consistency between pre-commit hooks and CI workflows, run a validation script that analyzes configuration files and confirms linting, type checking, and test commands align across both environments.

Linter configuration passing locally but failing in CI often happens when editorconfig, pre-commit hooks, and CI workflows are out of sync. Validating quality configuration alignment across these files resolves the issue.

You validate version consistency across project configuration files by running a consistency check that scans declared versions in editorconfig, linter configs, and CI workflows to ensure they match.

You need to validate your project quality configuration after setting up pre-commit hooks or before major releases to ensure a robust quality setup and prevent works locally, fails in CI issues.

Yes, you can use a consistency check to debug pre-commit hook setup by verifying that your .pre-commit-config.yaml file correctly aligns with your project's linter configurations and CI workflows.

Validating quality configuration requires no external dependencies, but it does need access to your project's configuration files and workflows to properly check alignment and version consistency.