claude-md-review
Audit a CLAUDE.md file for the patterns that actually degrade Claude Code's output — vagueness, unnamed files, stale facts, and bloat. Use when asked to review, audit, improve, shrink, or fix a CLAUDE.md, and when a project's results feel inconsistent or Claude keeps rediscovering the same context.
npx skills add wesammustafa/Claude-Code-Everything-You-Need-to-Know --skill claude-md-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CLAUDE.md Review Audit a `CLAUDE.md` against the failure modes that actually cost output quality. **Premise:** `CLAUDE.md` loads into context on every single session, so every line is either paying rent or costing you tokens on every turn forever. Most "the model isn't following instructions" problems are instruction problems. ## Steps 1. Read the target file (default `./CLAUDE.md`; also check `~/.claude/CLAUDE.md` and any nested `**/CLAUDE.md` if the project has them, since the closest one wins). 2. Score each dimension below and quote the specific lines that fail. 3. Output the report format at the bottom. Propose concrete rewrites, not "consider being more specific." ## What to check **Specificity** — the highest-leverage dimension. - Flag unfalsifiable directives: "write clean code", "follow best practices", "be careful", "use good naming". - Every rule should be checkable by reading a diff. `"Refactor functions over 40 lines"` is checkable; `"keep functions short"` is not. **Named anchors.** - Rules that reference "the config", "our API layer", or "the usual pattern" force rediscovery every session. Replace with real paths: `src/config/env.ts`, `src/api/client.ts`. - Verify
- Steps
- What to check
- Output format
- Rules
What does the claude-md-review skill do?
Audit a CLAUDE.md file for the patterns that actually degrade Claude Code's output — vagueness, unnamed files, stale facts, and bloat. Use when asked to review, audit, improve, shrink, or fix a CLAUDE.md, and when a project's results feel inconsistent or Claude keeps rediscovering the same context.
How do I install it?
Run `npx skills add wesammustafa/Claude-Code-Everything-You-Need-to-Know --skill claude-md-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From wesammustafa/Claude-Code-Everything-You-Need-to-Know, a repository with 2,483 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.