docs-update

Documentation synchronization can be automated by running a command within your Git repository that analyzes file changes and suggests updates for related documentation nodes based on predefined relationships.

Auditing outdated documentation is handled through incremental scanning, which saves and compares previous scans against current file changes to identify and suggest necessary documentation updates efficiently.

Graph-based documentation synchronization builds a graph of documentation nodes and their relationships, evaluating code changes against this map to detect outdated information and suggest targeted updates.

The scanning process supports customization, allowing you to define specific topics or handle individual documentation nodes so that synchronization focuses only on the areas you need.

Yes, this documentation verification operates within a Git repository context, requiring your project files and docs to be tracked in Git to detect changes and map relationships accurately.

Incremental scanning relies on predefined relationships and previous scan states, meaning newly added code files without established documentation node mappings may not be automatically detected for updates.