change-architecture-doc

You can automatically generate architecture documentation from git changes by analyzing git status and git diff to create or update docs with Mermaid diagrams. This process prioritizes existing documentation folders like docs or guides, falling back to the project root if none are found.

Documenting system boundaries and data flows after refactoring is best handled by analyzing git diffs to visualize structural changes. This approach focuses on structural modifications rather than implementation details, using Mermaid diagrams to map module interactions and impact areas.

Yes, you can use Mermaid diagrams to visualize module interactions in existing documentation folders. The system prioritizes directories like docs, packages/docs, guides, and documentation, automatically embedding system structure and flow diagrams into your current documentation setup.

To update architecture docs focusing on structural changes, analyze git changes to generate Mermaid diagrams of system boundaries and data flows. This method specifically targets structural modifications and impact areas, deliberately excluding implementation details from the generated documentation.

Yes, the architecture documentation generator works without a dedicated docs folder by falling back to the project root. It first searches for existing documentation directories such as docs, packages/docs, guides, or documentation, and generates the files in the root if none are found.

You can track event flows and impact areas using git diff analysis by generating architecture documentation with Mermaid diagrams. This visualizes system boundaries, module interactions, and data flows based on the structural changes detected in your git status.