update-visualizations

To keep Mermaid architecture diagrams accurate, you can analyze recent Git diffs to identify affected visualization files and automatically update the diagrams to match the evolving codebase. This ensures documentation stays aligned with actual project workflows.

Automatically updating documentation diagrams from a Git diff involves analyzing the code changes, mapping them to existing visualization markdown files, and editing or creating Mermaid diagrams using the project's README style guide for consistent formatting.

The tool looks for visualization configuration files by locating them via .devflow/visualizations.json, ~/.config/devflow/visualizations.json, or common docs folders. It reads the existing visualization index and files to determine what needs updating.

Yes, this diagram update workflow applies to projects that maintain visualization markdown files under a configured diagrams folder and use a README style guide. It requires this structure to locate configs and apply consistent formatting.

The best way to sync architecture visualizations with codebase updates is to use a change-aware workflow that analyzes recent Git changes, updates the affected Mermaid diagrams, and stages and commits the visualization artifacts with a descriptive message.

Missing workflow diagrams are handled through automated diagram creation, which generates the missing Mermaid visualizations using the project's style guide and updates the visualization index, or README, accordingly to maintain a complete documentation set.