validate-quality-config

Validate consistency across editorconfig, linter, pre-commit, and CI configurations.

12|Updated Dec 26, 2025

Search Tags:#version control #CI/CD #pre-commit hooks #consistency check #quality configuration

Ready to run

npx skills add https://github.com/jrjsmrtn/project-orchestration-skills --skill validate-quality-config

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate-quality-config
Source: https://github.com/jrjsmrtn/project-orchestration-skills/tree/main/skills/validate-quality-config
Command: npx skills add https://github.com/jrjsmrtn/project-orchestration-skills --skill validate-quality-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the common issue of inconsistencies in quality configuration files across a project, which can lead to "works locally, fails in CI" issues and affect release quality.

Core Features & Use Cases

Configuration Consistency: Validates the consistency between various configuration files such as .editorconfig, linter configs, .pre-commit-config.yaml, and CI workflow files.
Version Consistency: Checks that the declared version across the project files matches, ensuring version control integrity.
Pre-commit and CI Alignment: Confirms that pre-commit hooks are aligned with CI checks for linting, type checking, and tests.
Use Case: It is ideal for post setup-pre-commit to debug inconsistencies or before major releases to ensure a robust quality setup.

Quick Start

Run the validate-quality-config skill to check the consistency of your project's quality configurations.

Frequently Asked Questions about validate-quality-config

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

FAQPage Schema

How do I check consistency between pre-commit hooks and CI workflows?▼

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.

Why does my linter configuration pass locally but fail in CI?▼

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.

How do I validate version consistency across project configuration files?▼

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.

When do I need to validate my project quality configuration?▼

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.

Can I use a consistency check to debug pre-commit hook setup?▼

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.

Does validating quality configuration require any dependencies?▼

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.