Skill: Maintain CLAUDE.md Documentation

Overview

This skill defines when and how to proactively update CLAUDE.md files to keep them accurate and current.

Core principle: Keep documentation from being wrong. When you notice existing documentation is outdated or becomes stale due to code changes, correct it. This skill is only about fixing incorrect documentation, not adding new documentation (that may be covered by a different skill later).

When to Update CLAUDE.md

Watch for these signals that documentation needs updating:

Strong signals (update immediately):

• You notice outdated information while reading code - Commands, file paths, patterns, or conventions documented in CLAUDE.md don't match what you see in the actual codebase
• You make code changes that invalidate documentation - You rename files, change commands, modify patterns, or update architecture in ways that make existing documentation incorrect
• User corrects outdated information - User points out that documentation is wrong or stale
• You discover documentation contradicts reality - Testing patterns, file locations, or conventions are different from what's documented