What problem does it solve? Merging code without a thorough review lets bugs, security flaws, and convention violations slip into the main branch. This Skill acts as an automated second pair of eyes, auditing the full branch diff (git diff main...HEAD) before consolidation. ## Core Features & Use Cases - Multi-Dimensional Audit: Checks functional correctness and edge cases, test coverage, architectural conventions, early-stage security (secrets, injections, auth guards), and performance issues like N+1 queries. - Blocking vs. Non-Blocking Findings: Classifies issues as blocking (missing tests on critical logic, hardcoded credentials) or optional improvements, so teams know exactly what must be fixed. - Strict Report Template: Produces a standardized Markdown report with positives, blocking findings, suggestions, technical debt notes, and a final APPROVED / REQUEST CHANGES verdict. - Use Case: Before merging a feature branch that adds a new API endpoint, run this review to catch a missing auth middleware, an unhandled promise rejection, and a residual console.log in one structured report. ## Quick Start Review the diff of my current branch against main and give me a pre-merge report with blocking findings and a final verdict.
