Unlike a document you revise consciously, CLAUDE.md lives in the background of every conversation. You set it up, it works — and then time passes. You update your tools, change how you work, move clients, shift priorities. The file stays the same.
Over weeks and months, three specific problems accumulate:
Date headers drift. You added "as of January 2024" when you created the file. Your work has since evolved, but the date header stayed. Now it's misleading — Claude sees a date and may weight old context differently, or you see it and lose confidence in the file.
Work-in-progress markers survive. Notes like "TBD: verify this with legal" or "FIXME: confirm the API version" make sense during drafting. They stop making sense six months later when you forget they were there. They erode trust in the file.
Sections contradict each other. A project you archived still appears in the body. A process you retired still shows up in your instructions. These aren't dramatic conflicts — they're quiet contradictions that make Claude less reliable.
The Consistency checker catches all three automatically. Here's how.
The Consistency checker runs a static scan on your CLAUDE.md — no AI needed, just pattern matching. It looks for three categories of issue:
The checker finds every date reference in the file, identifies which ones appear in header lines (as of, last updated, last modified), and flags any header date that predates the newest date it finds in the body. If your file has "as of 2024-01-01" in a header but "June 2025" mentioned in the body, it flags the conflict and shows you both line numbers.
Lines containing any of these markers are flagged:
Each flagged line is reported with its line number and the first 60 characters of the text so you can find it quickly.
The checker identifies all ## headings in your file and detects when the same entity appears under mutually exclusive headings — for example, listed under both ## Archived Projects and ## Active Projects. Both line numbers are reported so you can decide which section the project belongs in.
The Consistency checker surfaces issues only. It does not:
It tells you what's wrong and where. You decide what to fix.
This is intentional. CLAUDE.md captures your voice, judgment, and way of working. Those things shouldn't be auto-edited. The Consistency checker is a diagnostic tool, not a rewriting tool.
The checker runs on the CLAUDE.md that the Analyzer generates from your conversations — so the Consistency results reflect what the Analyzer produced for your actual usage patterns.
A few maintenance habits keep CLAUDE.md reliable:
Practical guides and prompt patterns — no fluff, unsubscribe any time.