What problem does it solve? Teams need a consistent, read-only inspection pass that catches correctness bugs, architecture boundary violations, security concerns, and documentation drift before changes ship, without giving the inspector write access to the codebase. ## Core Features & Use Cases - Multi-dimension inspection: Covers correctness, edge cases, error handling, architecture and dependency boundaries, security and privacy side effects, maintainability, test gaps, unapproved scope expansion, and documentation drift between specs, code, and plans. - Read-only safety: Uses only inspection commands like git status, git diff, git log, grep, rg, and jq, with no edits, commits, or destructive Git operations. - Structured verdicts: Reports READY, CHANGES_REQUIRED, BLOCKED, or UNVERIFIED with findings ordered by severity and file/line evidence. - Use Case: Before merging a pull request, ask for a review of the diff to detect regressions, missing error handling, and drift between the updated code and its specification documents. ## Quick Start Review the current git diff for correctness issues, security concerns, and drift between the code and the specification documents.
