update-docs

Automatically update documentation by parsing changed files, mapping them to relevant documentation topics, and generating a structured plan to apply updates across the knowledge base. This keeps your docs aligned with the latest repository state.

Keeping a knowledge base in sync involves detecting code changes and cross-referencing them with existing documentation sections. This process generates a clear update plan to ensure consistency and reduce manual effort across the docs system.

Mapping code modifications to documentation sections requires parsing changed files and identifying relevant topics like AI SDK, UI components, or MCP integration. This structured mapping outputs a targeted plan for generating and applying necessary updates.

Yes, you can identify which docs need updates by analyzing repository changes and matching them to existing documentation topics. This determines whether documentation updates are required and outputs a structured plan for applying those changes.

Yes, the documentation update process works without external dependencies. It parses changed files internally, maps them to documentation topics, and outputs a structured plan to guide updates without requiring additional environment setup.

Automating documentation updates focuses on specific files like AI SDK and UI components docs. Limitations include relying on parsing changed files to map topics, meaning unmapped repository changes may not trigger necessary knowledge base updates.