sdcorejs-review-architecture

Run a cross-track architecture review checklist to detect layering violations, boundary breaches, and convention drift. It outputs Critical, Important, and Minor findings with file:line citations to pinpoint structural issues missed by per-file review.

Per-file review misses structural problems like circular dependencies, abstraction leaks, and missing module boundaries. A cross-track architecture audit checks for these systemic issues to ensure overall code organization aligns with conventions.

Use a cross-track architecture checklist to audit code structure for circular dependencies before major merges. It evaluates test placement and routes Critical findings with file:line citations toward an orchestration repair-loop for remediation.

Apply an architecture review checklist after refactoring to check for abstraction leaks and convention drift. It evaluates the codebase against documented conventions and outputs actionable severity findings with specific file:line citations.

Yes, an architecture audit can review test placement and module boundaries. The checklist evaluates whether tests live at the correct architectural layer and detects missing boundaries, reporting issues with severity levels and file:line citations.