What is the 'Iron Law' in this code review skill?

The Iron Law states that a quality review must never happen before spec compliance. You must first verify the code meets all requirements before evaluating its style or performance.

How are code review issues categorized?

Issues are classified into four severity levels: CRITICAL (must fix before merge), MAJOR (should fix), MINOR (style/small improvements), and NIT (optional stylistic preferences).

Can this skill help with security audits?

Yes, it includes a comprehensive security checklist covering input validation, authentication, secrets exposure, SQL injection, and CSRF protection.

Does it support frontend and UI code reviews?

Yes, it provides specialized checklists for UX and Accessibility (A11y), ensuring UI code handles loading states, error feedback, and screen reader compatibility.

Code Review Patterns

Name: Code Review Patterns
Author: romiluz13

byromiluz13

•

Collaboration Tools

Enforces a rigorous two-stage review process that prioritizes functional spec compliance before evaluating code quality, security, and performance.

About

The Code Review Patterns skill introduces a structured framework for high-stakes code audits within Claude Code. It operates on the 'Iron Law'—no quality review before spec compliance—ensuring that developers first verify that code actually works as intended before debating style or optimization. The skill provides detailed checklists for security vulnerabilities, performance bottlenecks, UX best practices, and accessibility standards, generating standardized reports with clear severity classifications from Critical to Nit.

Key Features

Deep-dive security checklists for SQLi, XSS, and authentication vulnerabilities
Standardized severity reporting for clear prioritization of fixes
Two-stage 'Spec-First' review workflow to ensure functional accuracy
Performance audit patterns to detect N+1 queries and resource leaks
Frontend-specific reviews for accessibility (A11y) and user experience
18 GitHub stars

Use Cases

Standardizing code review feedback across distributed engineering teams
Automating rigorous pull request audits for mission-critical codebases
Ensuring new features align perfectly with technical requirements and acceptance criteria

About

Key Features

Deep-dive security checklists for SQLi, XSS, and authentication vulnerabilities
Standardized severity reporting for clear prioritization of fixes
Two-stage 'Spec-First' review workflow to ensure functional accuracy
Performance audit patterns to detect N+1 queries and resource leaks
Frontend-specific reviews for accessibility (A11y) and user experience
18 GitHub stars

Use Cases

Standardizing code review feedback across distributed engineering teams
Automating rigorous pull request audits for mission-critical codebases
Ensuring new features align perfectly with technical requirements and acceptance criteria