What problem does it solve? Reviewing cross-cutting refactors, commits, and PRs in a layered Go CMS is hard because architectural invariants (ownership, dependency direction, cache coherence, runtime publication) are easy to break silently. This Skill provides a structured review procedure that scopes the analysis from the diff, traces only relevant execution paths, and classifies findings by severity. ## Core Features & Use Cases - Scoped review workflow: Starts from changed files, reads consumers of changed public contracts, and traces only relevant paths (boot/reload/request, read/write/invalidate, registration/compile/dispatch). - Severity classification: Ranks findings as Critical, Major, Medium, Minor, or acceptable trade-off, with current behavior, impact, smallest fix, and a regression test for material issues. - Invariant checklist: Covers kernel vs module vs adapter ownership, dependency direction, state lifetime, SiteRuntime publication, cache coherence, HTTP transport leakage, extension precedence, and module dependency ordering. - Use Case: After a PR modifies the cache invalidation layer, run this review to verify every mutation path preserves cached-read coherence before merging. ## Quick Start Ask the assistant to review the current diff or PR for GO CMS architecture invariant violations and produce a severity-ordered findings report.
