code-review-rules-conformance

To check rules conformance, audit the modified files in your pull request diff against every rule defined in `.claude/rules/` and the conventions in `CLAUDE.md`. The review generates a report citing the specific rule clause broken, severity, and why the change fails.

Diff analysis enforces conventions by performing a read-only, rule-by-rule audit of changed files. It matches modifications against project-specific rules in `.claude/rules/` and `CLAUDE.md`, classifying violations by severity to catch policy drift before merge.

No, you cannot automatically fix rule violations with this approach. The diff analysis is strictly read-only, producing a report-only response with no code edits. It identifies the specific rule clause broken and the severity, leaving modifications to the developer.

The best way to classify severity is to run a read-only diff analysis that checks changed files against the conventions in `CLAUDE.md` and `.claude/rules/`. It outputs actionable findings detailing the specific rule clause, severity level, and the reason for the violation.

You need your project-specific rules stored in `.claude/rules/` and guidance conventions defined in `CLAUDE.md` before checking modified files. The diff analysis uses these files as the baseline to audit changes and generate the violation report during a pull request.