What problem does it solve? Reviewing code changes for operational concerns like credentials, alarms, scale-out, cost, and environments is easy to skip or do inconsistently. This Skill applies a fixed catalog of Operations review lenses to a change so every review checks the same rules and produces a structured, evidence-backed report. ## Core Features & Use Cases - Scoped review: Reviews the current branch change, a commit, a range, a path, or the whole repository, reading files from git history when the scope is not checked out. - Static checker integration: Runs the bundled arch-check tool first, adopts its fully covered lens decisions, and judges the remaining lenses by reading the code. - Structured report: Outputs findings ordered by severity with file and line evidence, plus deviations backed by ADRs, passed, unverified, and not-applicable lenses. - Use Case: Before merging a pull request that adds a new alarm and changes deployment configuration, run this review to confirm the change satisfies the Operations lenses and to catch missing credential handling or undocumented environments. ## Quick Start Ask the assistant to run an Operations architecture review of the current branch change and report any findings with severity and file locations.
