Arch Review

Create a standalone HTML file that explains architectural changes from before to after. The artifact should help a reviewer understand what moved, why it moved, and where the new seams are.

Workflow

1. Establish the comparison base.

   • If the user names a branch, commit, PR, diff, or file set, use that.
   • Otherwise inspect git state and choose the safest obvious base: merge-base with the main branch, the previous commit, or unstaged changes.
   • Completion criterion: every changed file in scope has a clear before/after source.

2. Inventory the architecture.

   • Identify modules, packages, entry points, exported types, public functions, adapters, boundaries, and cross-module dependencies.
   • Prefer static analysis tools already present in the repo; otherwise use rg, language-aware parsers, import graphs, and targeted file reads.
   • Completion criterion: every changed module and every direct dependency crossing its boundary is accounted for.