Architecture Impact

To analyze architecture impact, you can assess uncommitted changes, specify a git range, or analyze the last N commits. This process identifies code modifications and determines whether architecture documentation requires corresponding updates.

Architecture impact analysis identifies whether code changes in component repositories affect existing architecture documentation. You need this process when updating code to ensure your architecture repository stays synchronized with structural modifications.

You can check documentation update requirements by running a directory-based analysis across component repositories. The tool generates a structured report detailing affected documents and recommended updates based on your code changes.

Yes, git is a required dependency for architecture impact assessment. The tool uses git to process uncommitted changes, specified commit ranges, or the last N commits to evaluate documentation impacts.

The best way to review uncommitted changes is using a comprehensive directory-based analysis across component repositories. This approach evaluates the changes in a single pass and produces a structured impact report.

Yes, you can use architecture impact analysis for specific git commit ranges by providing parameters like --range main..HEAD. The tool evaluates the specified commits and identifies affected architecture documents.