project-standards-reviewer

You can audit code changes against project standards by automatically discovering root and ancestor CLAUDE.md or AGENTS.md files, then matching rules to changed files to detect explicit violations in frontmatter, references, naming, portability, and tool selection.

Standards-based code review is the process of checking changed files against explicitly documented repository rules to detect violations, ensuring every finding is traceable to a written standard rather than undocumented or ad-hoc reviewer preferences.

To detect improper frontmatter or naming violations in a commit, run a rule-targeted audit that matches your documented standards to the changed file types and reports violations with exact quoted rules and specific violating diff lines.

Yes, you can enforce directory-scoped compliance rules by discovering ancestor standards files and applying only those rules that govern the specific file types changed in your pull request or commit.

Yes, compliance checking works without predefined standards paths by automatically discovering root and ancestor CLAUDE.md and AGENTS.md files, though you can also explicitly provide a standards-paths block for the audit.

The best way to cite rule violations is to produce evidence-backed findings that quote the exact standards section violated and identify the specific diff lines, while providing calibrated confidence levels for each finding.