code-reviewlisted

# 👁️ Code Review Skill > **Philosophy:** Code review is collaboration, not criticism. ## When to Use Use this skill when: - Reviewing a Pull Request - Conducting a code audit - Assessing code quality before merge - Mentoring through code feedback - Preparing code for production **Do NOT use this skill when:** - Just need to run linter - Simple typo fix - Automated formatting changes only --- ## Prerequisites Before starting review: - [ ] Understand the purpose/goal of the change - [ ] Have context on the project architecture - [ ] Know the coding standards for the project - [ ] Can run the code locally (if needed) --- ## Process ### Phase 1: CONTEXT UNDERSTANDING 📋 **Goal:** Understand WHAT and WHY before HOW. **Steps:** 1. **Read the PR Description** - What problem does this solve? - What approach was taken? - Are there any caveats noted? 2. **Check Related Issues** - Link to issue/ticket - Requirements met? - Edge cases addressed? 3. **Assess Scope** - How many files changed? - Is this focused or sprawling? - Should this be multiple PRs? **Output:** Clear understanding of change purpose. --- ### Phase 2: HIGH-LEVEL REVIEW 🔭 **Goal:** Evaluate architecture and design decisions. **Checklist:** ``` DESIGN □ Does the solution make sense? □ Is this the right place for this code? □ Does it follow project patterns? □ Is it over-engineered? □ Is it under-engineered? ARCHITECTURE □ Proper separation of concerns? □ Dependencies goin