What problem does it solve? Reviewing Spring Boot pull requests by hand often misses production risks hidden behind framework behavior—proxies, transactions, JPA fetch plans, security boundaries—while flooding authors with cosmetic nitpicks. This Skill performs a disciplined, read-only review of a diff, commit, or working-tree change and reports only verified, severity-ranked defects. ## Core Features & Use Cases - Risk-ordered review: Traces each change from REST entry points through services, persistence, and external systems, prioritizing security, correctness, concurrency, and data integrity over style. - Evidence-gated findings: Every reported issue includes location, evidence, triggering scenario, production impact, remediation direction, and a verification test—unproven concerns become questions or gaps, not defects. - Owner-skill coordination: Routes each finding to the skill that owns the rule (testing, security, JPA, patterns) instead of inventing standards, and records coverage, revision, and verification gaps. - Use Case: Ask for a review of a pull request that adds a new endpoint with caching; the Skill checks tenant scoping of cache keys, transaction-aware eviction ordering, contract compatibility, and required test boundaries, then delivers a merge-decision-ready report. ## Quick Start Review the current pull request of this Spring Boot project and list any blocking findings with evidence and suggested fixes.
