documentation-maintenance

To keep documentation in sync with code changes, run a pre-PR documentation audit using a checklist to verify project files, skill files, and CLAUDE.md reflect recent features and architectural modifications. This prevents outdated information and knowledge gaps.

Documentation drift occurs when project docs become outdated relative to code. Prevent drift by integrating maintenance checklists into commit and PR workflows, ensuring new features, bug fixes, and architectural changes are documented immediately during development.

Update CLAUDE.md and skill files by following targeted documentation guidance based on the specific code change type. This ensures learnings and architectural modifications are recorded in the correct files, preserving institutional knowledge across the project.

Perform a documentation maintenance check before creating a pull request. Running this pre-PR audit ensures all relevant files are updated with new logic and examples, enforcing documentation standards and preventing knowledge loss during code reviews.

Yes, you can enforce documentation standards by integrating maintenance checklists into commit and PR workflows. This guides users to document new features and bug fixes before submission, ensuring project documentation remains current and accurate.