convention-audit

To check code compliance, parse project files to automatically detect deviations from directory structures, naming conventions, and import practices. This continuous enforcement reduces manual effort and ensures consistency across large codebases.

Yes, you can use this for pre-merge checks and code reviews in large codebases. It automatically detects style compliance issues, improper imports, and structural deviations, ensuring continuous code quality enforcement before merging.

The best way to validate variable naming conventions and file headers is to parse the code for style and required documentation. This process identifies deviations from established standards and ensures proper documentation is present.

To audit import order and avoid forbidden patterns, run an automated style and import audit across project files. This detects non-compliant import practices and enforces code style consistency according to your project standards.

No specific dependencies or external linting tools are required. The code review process operates independently by parsing code directly for style, headers, imports, and directory structures to identify deviations from coding standards.