ix-architecture

You can detect code smells and coupling risks by analyzing an Ix graph to assess subsystem structure and crosscutting signals. It computes cohesion, coupling, and smell severity without requiring direct file scanning.

The best way to analyze architecture health is by running a scoped graph analysis on your target subsystem path. This evaluates coupling, crosscutting concerns, and architecture smells to provide early risk detection before refactoring.

Graph reasoning identifies dependency hotspots by ranking high-impact components based on their dependents. It highlights areas where smells or coupling indicate significant risk within the assessed subsystems.

Yes, you need an Ix graph available to run architecture analysis. The assessment computes design health metrics and detects smells entirely from graph data rather than scanning repository files directly.

Yes, you can optionally save architecture health reports to a file. This allows you to document subsystem structure, detected smells, and ranked hotspots for later review or team documentation.

When Pro is present, the analysis appends recorded design decisions that relate to the findings. This cross-references your architecture smells and coupling risks with historical design decisions.