Check Conventions

Enforce repository conventions by translating ALWAYS/NEVER/MUST directives from rules files into line-level checks. The process generates deterministic PASS/FAIL reports with line numbers and directive text to ensure auditable PR reviews.

Static analysis maps documentation rules by loading directives from documentation/rules/*.md and .cursor/rules/*.mdc files. It then scans tracked code areas to report deterministic PASS/FAIL results with exact line numbers and the matched directive text.

Yes, you can check code conventions by loading rules from markdown files in documentation/rules/*.md and .cursor/rules/*.mdc. The tool applies these directives to all tracked code areas to identify violations with precise line numbers.

Automate code review for directives by converting ALWAYS/NEVER/MUST rules into deterministic, read-only checks. This approach reduces human review cycles by generating line-numbered PASS/FAIL reports integrated directly into PR quality gates.

Yes, check-conventions works with .cursor rules files by loading directives from .cursor/rules/*.mdc alongside documentation/rules/*.md. It performs static analysis to resolve scope and report line-level convention violations deterministically.

Deterministic convention checks are limited to rules defined as ALWAYS/NEVER/MUST directives in loaded markdown files. They provide read-only, auditable PASS/FAIL reports based on static analysis without modifying the target code.