code-review-rules-conformance

Audit changed code against project rules in .claude/rules and CLAUDE.md.

5|Updated Mar 24, 2026

Search Tags:#diff analysis #code review #pull request #claude.md #severity #rules conformance

Ready to run

npx skills add https://github.com/ably/ably-ai-transport-js --skill code-review-rules-conformance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-rules-conformance
Source: https://github.com/ably/ably-ai-transport-js/tree/main/.claude/skills/code-review-rules-conformance
Command: npx skills add https://github.com/ably/ably-ai-transport-js --skill code-review-rules-conformance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps reviewers verify that changed code follows the project's own rules and conventions, so policy drift and review misses are caught early.

Core Features & Use Cases

Rule-by-rule auditing: Checks each changed file against every rule in .claude/rules/ and the conventions in CLAUDE.md.
Actionable findings: Reports violations with the specific rule clause, severity, and why the change breaks the rule.
Read-only review workflow: Fits pull request reviews and local diff inspections where the goal is validation, not modification.

Quick Start

Ask the assistant to review the current diff for rules conformance against .claude/rules/ and CLAUDE.md.

Frequently Asked Questions about code-review-rules-conformance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check my pull request diff for 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.

How does diff analysis enforce project conventions during a code review?▼

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.

Can I automatically fix rule violations found during the diff analysis?▼

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.

What is the best way to classify severity for code review violations against CLAUDE.md?▼

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.

Do I need to configure anything before checking modified files for rules conformance?▼

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.