repo-architecture-review

Architectural drift analysis identifies structural degradation by surfacing modules, runtime boundaries, and state ownership. This skill performs a source-grounded review of bounded repository slices, producing a structured findings artifact that documents layering, coupling, and governance without editing code.

Document architectural governance by running a findings-first review scaffold on a repository packet. This generates a structured architecture map and review artifact detailing boundaries and drift surfaces, ensuring no code is edited or merge decisions are made during the analysis.

Yes, you can analyze a bounded repository slice instead of the full codebase. The skill is designed to work with CodeBuddy review packets and bounded slices, allowing you to surface architectural boundaries and drift surfaces for specific sections of your project.

The best way to map runtime boundaries and state ownership is by applying a deterministic architectural review scaffold. This produces an architecture map that explicitly details module coupling, state ownership, and drift surfaces within your repository slice.

Yes, the architectural review output includes handoff candidates for downstream documentation. The structured artifact identifies diagram-author, adr-curator, and architecture-fitness-function-author roles to facilitate subsequent documentation and governance tasks.