sk-code-review

Automated code review produces findings-first, severity-ordered issues with P0/P1/P2 classifications and file:line evidence. Point the review process at your PR diff to generate an actionable report enforcing security and correctness minimums across any tech stack.

A findings-first code review prioritizes severity-ordered issues over style checks, enforcing baseline security and correctness minimums regardless of the tech stack. It delivers concrete file:line evidence and actionable fixes rather than passing subjective stylistic commentary.

Yes, automated code review applies across any tech stack by using a baseline configuration with a single overlay like opencode or web. The overlay supplies stack-specific style and verification commands while the baseline enforces security minimums for merge gates.

Overlays supply stack-specific style and verification commands while the baseline enforces core security and correctness minimums. Overlay precedence dictates style and verification rules, ensuring the review adapts to the framework while maintaining mandatory security checks.

Automated code review supports PR reviews, merge gates, and risk assessments by applying a baseline with an opencode or web overlay. It outputs a structured report with explicit next steps, enforcing minimums to ensure quality and security across the evaluated code.

Baseline code review enforces security and correctness minimums but lacks stack-specific style and verification rules without an overlay. You need to apply a single overlay like opencode or web to supply the framework-specific commands required for complete review coverage.