doc-update

To update project documentation when code changes, you can analyze code diffs to identify impacted schemas, APIs, and design docs, then apply those changes across .ai_docs and project_doc sections to keep everything in sync.

Keeping .ai_docs synchronized with schema updates involves analyzing code diffs to detect schema changes and applying those updates directly to schema tables, context docs, and design pages with built-in validation and error handling.

Analyzing code diffs helps with documentation synchronization by identifying exactly which features, bug fixes, or schema changes occurred, allowing targeted updates to API docs, references, and data-model sections without manual review.

You need to update API docs and design pages after a feature release whenever code changes introduce new functionality, fix bugs, or alter data models, ensuring project_doc and references accurately reflect the current codebase.

Automatic documentation update works for both bug fixes and new features by analyzing the underlying code diff for either type of change and applying the necessary updates across all impacted documentation artifacts.

A limitation of syncing project docs automatically is that it relies on analyzing code diffs, meaning documentation accuracy depends on the clarity of the diff and may require validation to ensure complex design pages and contexts are correctly updated.