vibe-rules

You can identify duplicate and conflicting Claude rules by scanning global, project, and agent directories including ~/.claude/rules/common/, .claude/rules/, .agent/rules/, and CLAUDE.md to enforce cross-source consistency and prevent rule drift.

Claude rule drift happens when global, project, and agent rule sets diverge across multiple repositories. Unmanaged duplicates and conflicting instructions across ~/.claude/rules and CLAUDE.md references cause inconsistent agent behavior and governance gaps.

To validate missing agent rule mappings, scan CLAUDE.md references to verify that all required agent rules are present. This process flags missing mappings and generates an actionable cleanup plan to restore reference integrity.

Yes, you can check Claude rules for conflicts across global and project scopes. The process validates references and detects duplicates spanning ~/.claude/rules/common/ and .claude/rules/ directories to ensure multi-scope consistency.

Generate a cleanup report for Claude rule conflicts by running a scan to identify duplicates and missing references. This produces a detailed report with actionable cleaning steps to resolve inconsistencies across your rule sets.

The best way to manage Claude rules governance in a multi-repo setup is to perform regular cross-source consistency checks. Detecting duplicates and validating references across global, project, and agent directories prevents rule drift and maintains alignment.