Code Review for TypeScript React: What to Look For

I've reviewed over 1,000 React PRs. Early on, I nitpicked everything: indentation, variable names, comment styles. My reviews were long, exhausting, and ineffective. Developers got defensive. Important issues slipped through while I argued about semicolons. Then I learned to distinguish between what matters and what doesn't. I started catching bugs that would have shipped. I helped junior developers grow. My reviews became shorter but more valuable. Here's what I look for now—organized by impact. Not style guides. Not preferences. The things that actually matter. The Review Priority Pyramid High Priority (Must Fix) ├─ Security vulnerabilities ├─ Type safety violations ├─ Logic bugs └─ Performance issues Medium Priority (Should Fix) ├─ Architecture concerns ├─ Accessibility issues ├─ Missing tests └─ Poor error handling Low Priority (Nice to Have) ├─ Code organization ├─ Naming improvements └─ Minor optimizations Ignore ├─ Personal style preferences ├─ Subjective opinions └─ Bikesheddin