audit

Audit CLAUDE.md and planning documents to detect drift and stale references.

2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/MusserLab/lab-claude-skills --skill audit-musserlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/MusserLab/lab-claude-skills/tree/main/skills/audit
Command: npx skills add https://github.com/MusserLab/lab-claude-skills --skill audit-musserlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps project documentation healthy and aligned by regularly auditing CLAUDE.md, planning docs, and conventions to catch drift before milestones.

Core Features & Use Cases

  • Detect project type to tailor the audit scope based on a project-type field in CLAUDE.md.
  • Cross-check CLAUDE.md against planning documents to identify stale or duplicated content and suggest pointers to planning docs when appropriate.
  • Assess planning document health, including collapsed vs detailed phases, Next Session items, and overall size, flagging opportunities to consolidate.
  • Identify unregistered documents and scripts, proposing additions to planning documents and guiding lifecycle improvements.
  • Prune self-evident conventions and monitor CLAUDE.md size to improve readability and maintainability.
  • Provide a user-level health check for local Claude setups, flagging memory, user CLAUDE.md size, and personal skill drift.

Quick Start

Run a full project health audit to detect drift between CLAUDE.md, planning docs, and scripts.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I detect documentation drift between project planning docs and conventions?

To detect documentation drift, cross-check CLAUDE.md against planning documents to identify stale references, duplicated content, and missing planning signals before project milestones. This audit flags inconsistencies and suggests actionable pointers to realign project health.

What is the best way to audit project health and identify unregistered scripts?

The best way to audit project health is to scan your project registry and planning documents to identify unregistered scripts and documents. The audit proposes registry additions and guides lifecycle improvements to maintain data integrity.

Why does my CLAUDE.md file keep growing with self-evident conventions?

Your CLAUDE.md grows because unmanaged conventions accumulate over time. A project audit prunes self-evident conventions and monitors file size constraints, improving overall readability and maintainability.

Can I assess planning document health for collapsed phases and next session items?

Yes, you can assess planning document health by evaluating collapsed versus detailed phases and checking Next Session items. The audit flags consolidation opportunities and verifies your planning docs meet size constraints.

Do I need a project-type field in CLAUDE.md to tailor the audit scope?

Yes, including a project-type field in CLAUDE.md allows the audit to detect your project type and tailor the audit scope accordingly. This ensures documentation and convention checks align with your specific project governance requirements.

How do I run a user-level health check for local Claude setups and personal skill drift?

Run a full project health audit to check local Claude setups, flagging memory issues, user CLAUDE.md size limits, and personal skill drift. This identifies configuration degradation and keeps local project documentation aligned.