code-review-rules-drift

To check if code review rules are outdated after a refactor, audit your rule guidance for drift against the current codebase. This process flags renamed symbols, removed behavior, and outdated examples in your .claude/rules and CLAUDE.md files.

Your CLAUDE.md documentation references non-existent symbols because rule guidance has drifted from the current codebase after recent changes. Auditing rule files against the implementation catches these stale conventions and flags missing guidance for new behaviors.

You need to audit rule files for documentation drift after refactors, feature removals, API changes, and updates to team conventions. This ensures your .claude/rules and CLAUDE.md files capture new conventions and avoid referencing removed behavior.

You can detect missing conventions in CLAUDE.md by running a read-only review of affected files after code changes. This produces a conformance-style report pointing back to affected rules, highlighting new conventions that should be documented.

The best way to keep coding conventions aligned with the codebase is auditing rule guidance for drift against the current implementation. This approach generates principle-level recommendations that avoid fragile implementation details while catching stale examples.

To review the latest code change for rules drift in .claude/rules, request a read-only review of the affected files. This generates severity-based findings that identify stale or missing guidance caused by recent symbol renames or behavior changes.