claude-md-review

Review CLAUDE.md structure, redundancy, staleness, and completeness with a 1-10 rating.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/blucsigma05/tbm-apps-script --skill claude-md-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-md-review
Source: https://github.com/blucsigma05/tbm-apps-script/tree/main/.claude/scheduled-tasks/claude-md-review
Command: npx skills add https://github.com/blucsigma05/tbm-apps-script --skill claude-md-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces confusion and wasted effort caused by CLAUDE.md becoming unclear, redundant, outdated, or missing critical enforcement details.

Core Features & Use Cases

  • Structure and readability auditing: Checks whether related topics are grouped logically or scattered.
  • Redundancy detection: Identifies duplicated statements and repeated guidance that should be consolidated.
  • Staleness and coverage review: Flags broken references to files or patterns that no longer exist and finds gaps between what the code enforces and what the docs explain.
  • Optimization for concision: Rates bloat and suggests removals or streamlining.

Quick Start

Run this skill to review the contents of CLAUDE.md end-to-end and post an effectiveness report and, if the rating is under 8, a concrete restructure plan.

Frequently Asked Questions about claude-md-review

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

FAQPage Schema
How do I review my CLAUDE.md documentation for staleness and redundancy?

To review CLAUDE.md documentation for staleness and redundancy, run an end-to-end audit that evaluates structure, flags broken file references, and detects duplicated statements, producing a 1-10 effectiveness rating with specific findings and a concrete restructure plan if the score is below 8.

What causes AI-agent instruction files to become bloated or unclear?

AI-agent instruction files become bloated or unclear when critical enforcement details are missing, related topics are scattered, or guidance is duplicated. Reviewing documentation effectiveness helps identify these gaps and suggests removals to optimize concision.

How do I audit a pattern registry for broken references and missing enforcement details?

To audit a pattern registry for broken references and missing enforcement details, run a staleness and coverage review. This process flags references to patterns that no longer exist and finds gaps between what the code enforces and what the documentation explains.

What is the best way to restructure project documentation when it gets a low effectiveness rating?

The best way to restructure project documentation when it gets a low effectiveness rating is to follow a concrete restructure plan. This plan is automatically generated when a documentation review scores below 8, providing specific steps to consolidate bloat and group scattered topics logically.

Does this documentation review process require any external dependencies or components?

No, this documentation review process does not require any external dependencies or components. It operates independently to evaluate structure, redundancy, staleness, ordering, completeness, and bloat within your existing CLAUDE.md files.