code-review-web

1# Code Review for Web
2 
3Review 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.
4 
5---
6 
7## When to use
8 
9- Reviewing a pull request before merging
10- Debugging a production issue
11- Investigating a build failure
12- Auditing security or performance of existing code
13- Investigating environment variable or configuration issues
14- Triaging a "the site is broken" report
15 
16## When NOT to use
17 
18- Writing a new feature spec (use `pm-spec-writing`)
19- Pre-launch QA against the running site (use `qa-testing`)
20- Performance deep-dive on Core Web Vitals (use `performance-optimization`)
21- Deep accessibility compliance review (use `accessibility-audit`)
22 
23---
24 
25## Required inputs
26 
27- The code, PR, error message, or symptom under review
28- Access to logs (build logs, function logs, server logs) if debugging
29- The stack (framework, hosting, database) - even at high level
30 
31If just a symptom is provided ("the site is broken"), the workflow's first step is gathering enough context to investigate.
32 
33---
34 
35## The framework: 5 review dimensions
36 
37Every code review covers five dimensions. Pick the depth based on the situation.
38 
39### 1. Correctness
40 
41Does the code do what it claims to do?
42 
43- Logic matches the intent stated in the spec or PR description
44- Edge cases handled (empty states, error states, network failures)
45- Off-by-one errors, null/undefined handling, async race conditions
46…