rules-auditor

Audit Claude Code guidelines for coverage gaps and outdated rules.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/iamsteveholmes/momentum --skill rules-auditor-iamsteveholmes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rules-auditor
Source: https://github.com/iamsteveholmes/momentum/tree/main/skills/momentum/skills/agent-guidelines/sub-skills/rules-auditor
Command: npx skills add https://github.com/iamsteveholmes/momentum --skill rules-auditor-iamsteveholmes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits Claude Code guidelines in a project to identify coverage gaps, outdated rules, and misalignments with current technology guidance.

Core Features & Use Cases

  • Inspects .claude/rules/ recursively to extract path patterns and topics.
  • Reads CLAUDE.md and .claude/CLAUDE.md (if they exist) to capture tech-specific instructions and imports.
  • Highlights gaps and staleness when rules or verifications are missing or outdated.

Quick Start

Run an audit against the current repository to surface coverage gaps and recommended updates.

Frequently Asked Questions about rules-auditor

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

FAQPage Schema
How do I audit Claude Code guidelines for coverage gaps in my project?

Auditing Claude Code guidelines involves scanning .claude/rules/ recursively and reading CLAUDE.md files to extract path patterns, topics, and imports, then highlighting coverage gaps, staleness, and potential improvements.

What does a Claude Code rules audit check for in a repository?

A Claude Code rules audit checks for coverage gaps, outdated rules, and misalignments with current technology guidance. It captures version pins, last-verified dates, and imports to surface staleness and missing rule verifications.

How do I find outdated or stale rules in my .claude directory?

Finding outdated rules in your .claude directory requires scanning .claude/rules/ to extract path patterns and topics, then flagging rules missing last-verified dates or version pins as stale and outdated.

Can I audit a repository if I only have a CLAUDE.md file and no .claude folder?

Yes, you can audit a repository with only CLAUDE.md. The audit reads CLAUDE.md and .claude/CLAUDE.md if they exist, capturing tech-specific instructions and imports even without a full .claude/rules/ directory structure.

What is the best way to surface version pins and last-verified dates in Claude Code rules?

Surfacing version pins and last-verified dates requires auditing .claude/rules/ recursively and reading CLAUDE.md files, capturing these details into a structured report highlighting coverage gaps, staleness, and potential improvements.

Why does my Claude Code rules audit show coverage gaps after updating dependencies?

Coverage gaps appear after dependency updates because existing rules become misaligned with current technology guidance; auditing captures these gaps, outdated version pins, and stale last-verified dates needing updates.