update-docs

To update documentation after code changes, this Skill detects modifications across your codebase and refreshes files like README.md, CLAUDE.md, and assistant-knowledge.ts to keep project docs synchronized with the latest code.

Keeping your README in sync with your codebase is achieved by applying per-file update rules during CI or local development. It enforces pre-flight checks to selectively update file lists and maintain accurate project onboarding guides.

Yes, you need a clean git status before updating project docs. The process prevents accidental updates when the git working tree is dirty to avoid generating partial or inconsistent documentation.

The best way to maintain consistent documentation across developer guides is to automate updates for files like CLAUDE.md and assistant-knowledge.ts after committing changes. This prevents outdated onboarding references and saves time.

Yes, the documentation update process explicitly applies to assistant-knowledge.ts files across the repository. It enforces selective file lists and explicit pre-flight checks to update them alongside standard markdown docs.