convention-check

To automate project convention checks, configure a `.convention-check.json` file to define rules and use OVERRIDES.md for exceptions. The tool scans the repository, compares code against CLAUDE.md standards, and reports violations with clear guidance.

Enforcing coding and architectural conventions across plugin projects is done by validating configuration files and applying local overrides. The scanner reads project standards from CLAUDE.md and reports deviations automatically.

Static analysis for project conventions handles local rule exceptions through an OVERRIDES.md file. You define specific exceptions there, and the checker applies these overrides alongside the `.convention-check.json` configuration during the repository scan.

You cannot effectively use this convention checker without a CLAUDE.md file, as it serves as the primary source for project standards. The tool relies on comparing local repository rules against these defined standards to identify and report violations.

Project convention validation may report false positives if local exceptions are not properly defined. Ensure your specific use cases are documented in OVERRIDES.md and your `.convention-check.json` configuration accurately reflects your intended coding guidelines.

You need to configure a `.convention-check.json` file to manage applied rules before scanning for code quality violations. This file works with CLAUDE.md standards and OVERRIDES.md to ensure the automated validation matches your project requirements.