architectural-review

To enforce module boundaries and dependency direction in a pull request, validate architectural integrity by checking that dependencies follow repository rules like CLI to SDK, ensuring the SDK never depends on the CLI.

Architectural erosion is the gradual degradation of a system's structure during refactoring. You prevent it by applying an architectural review checklist to verify invariants like module boundaries and API export surfaces before merging changes.

You validate API surface changes and detect unsafe cross-package imports by reviewing barrel exports and checking import statements against repository dependency rules during the pull request review process.

You should perform an architectural review when a pull request introduces new modules, modifies dependencies, changes API export surfaces, or executes sweeping refactors that affect core architecture invariants.

Yes, you can apply automated architectural review checks to guard bootstrap file constraints, validate module dependencies, and flag sweeping architectural changes for structured review and guardrails.