code-review-context-analyzer

To generate an architecture diagram from a pull request diff, provide the raw code changes to the analyzer. It outputs Mermaid diagrams that map module interactions and visualize the structural impact of the modifications.

The best way to summarize a large git diff is to use an analyzer that switches to module-level summaries. It filters out trivial changes and provides concise intent walkthroughs to accelerate the review process.

Yes, you can automatically flag security-sensitive changes in a merge request. The analyzer evaluates the provided code diff during processing and explicitly highlights modifications that are security-sensitive.

Yes, the code analyzer resolves cross-file dependencies in pull requests. It traces modified code across multiple files to generate an accurate logic walkthrough and a comprehensive architectural view.

To understand the intent behind code changes in a git diff, run the analysis to generate an intent summarization. This report explains the 'why' and 'how' of the modifications for faster reviewing.

You should use module-level summaries instead of full diff analysis when handling large diffs. This approach prevents information overload by providing high-level architectural overviews rather than line-by-line details.