doc-sync

Documentation sync automatically detects discrepancies between your CLAUDE.md, .env.example, and .env.production.example files against current codebase state. It applies updates across all three files after environment changes or skill additions, then proposes a Git commit message to track changes.

Yes. The skill generates or updates a skills section in CLAUDE.md listing available Claude Skills with descriptions and use cases whenever you add new skills or request documentation updates.

Documentation sync focuses on three files: CLAUDE.md for project guides, .env.example for local configuration templates, and .env.production.example for production environment templates. It ensures all three stay consistent with your actual setup.

By validating documentation against current project setup and automatically detecting drift between files and codebase state, it eliminates developer confusion from outdated onboarding guides and environment configuration inconsistencies.

Yes. After applying documentation updates, it generates pre-formatted Git commit messages that streamline version control, ensure clear changelogs, and provide traceability for all documentation modifications.

Run documentation sync after adding new skills, making significant environment setup changes, or receiving requests to update docs. This ensures CLAUDE.md and environment templates reflect your current project state before committing changes.