project-standards-reviewer

To automate pre-merge checks for coding conventions, audit pull request changes directly against your documented CLAUDE.md and AGENTS.md files. This enforces written rules by citing exact sources for every violation, preventing inconsistent code from merging.

Standards-aware code review audits changes exclusively against your project-specific standards files rather than applying generic best practices. It eliminates guesswork by citing exact rule sources from CLAUDE.md or AGENTS.md for every reported violation.

Yes, you can check frontmatter compliance and cross-reference validity in agent files before merging. The reviewer audits these specific elements against your documented standards to catch broken links and formatting errors pre-merge.

Yes, the reviewer enforces cross-platform portability checks if those rules are explicitly documented in your AGENTS.md files. It only applies project-written rules and does not guess or apply generic portability best practices.

To ensure tool selection policies are followed in a pull request, audit the code changes against your repository's standards files. The reviewer identifies non-compliant tool usage by citing the exact policy defined in your documentation.

The limitation of this compliance audit approach is that it only enforces explicitly documented rules. It will not catch violations for unwritten conventions or infer generic best practices, requiring comprehensive documentation to be effective.