update-claudemd

To keep CLAUDE.md up-to-date, you can run a skill that analyzes recent git commits and updates the file to reflect new modules, public APIs, architecture, and development command modifications.

Automating CLAUDE.md updates involves reviewing recent git changes to identify significant code modifications, then applying those architectural shifts and component additions directly into the documentation file.

Reviewing git commits improves developer onboarding by capturing significant codebase modifications, ensuring the central CLAUDE.md documentation file accurately reflects current project architecture and testing patterns.

The update-claudemd skill requires no external dependencies to review code, operating solely on git history analysis to detect new modules, dependencies, and public API changes.

You should avoid automated git history analysis for documentation when recent commits contain only minor or insignificant code modifications that do not impact public APIs, architecture, or testing patterns.

Yes, you can use this skill to document new testing patterns and component additions, as it specifically focuses on capturing these significant codebase modifications during the CLAUDE.md update process.