eval-rules

Auditing Claude rule files involves discovering all .claude/rules/ entries, validating YAML frontmatter and paths patterns, and interactively confirming each rule's relevance against your actual project files.

Validating Claude rules frontmatter involves checking for proper YAML definitions and verifying that paths patterns have adequate coverage against the codebase to ensure rule hygiene and applicability.

Yes, you can interactively review Claude rules during an audit session, confirming or improving each rule's scope and usefulness while optionally updating the rule files in place based on your feedback.

You can check if Claude rules match real project files by running an audit that validates pattern coverage against the codebase, ensuring each rule's scope aligns with the actual files in your repository.

The best way to maintain rule hygiene is to run regular interactive audit sessions that validate frontmatter, check pattern coverage, and produce a structured report to confirm or improve each rule's applicability.

No dependencies are required to validate Claude rules directories; the audit workflow operates independently to discover rule files, validate frontmatter, and generate structured reports.