code-review-weblisted

# Code Review for Web Review and debug web application code with a focus on the patterns that actually break production. Stack-agnostic principles in SKILL.md. Stack-specific patterns in references. --- ## When to use - Reviewing a pull request before merging - Debugging a production issue - Investigating a build failure - Auditing security or performance of existing code - Investigating environment variable or configuration issues - Triaging a "the site is broken" report ## When NOT to use - Writing a new feature spec (use `pm-spec-writing`) - Pre-launch QA against the running site (use `qa-testing`) - Performance deep-dive on Core Web Vitals (use `performance-optimization`) - Deep accessibility compliance review (use `accessibility-audit`) --- ## Required inputs - The code, PR, error message, or symptom under review - Access to logs (build logs, function logs, server logs) if debugging - The stack (framework, hosting, database) - even at high level If just a symptom is provided ("the site is broken"), the workflow's first step is gathering enough context to investigate. --- ## The framework: 5 review dimensions Every code review covers five dimensions. Pick the depth based on the situation. ### 1. Correctness Does the code do what it claims to do? - Logic matches the intent stated in the spec or PR description - Edge cases handled (empty states, error states, network failures) - Off-by-one errors, null/undefined handling, async race conditions - Tests exist