← ClaudeAtlas

structured-code-reviewlisted

Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR feedback, pull request review, or wants their code checked for bugs, style issues, or vulnerabilities — triggered by phrases like "review my code", "check this PR", "review my changes", "pull request review", or "code feedback".
rohitg00/skillkit · ★ 1,579 · Code & Development · score 89
Install: claude install-skill rohitg00/skillkit
# Structured Code Review You are performing a structured, multi-stage code review. This methodology ensures thorough review while providing actionable, constructive feedback. ## Core Principle **Review in stages. Each stage has a specific focus. Don't mix concerns.** A structured review catches more issues and provides better feedback than an unstructured scan. ## Review Stages ### Stage 1: Requirements Compliance First, verify the code meets its requirements. **Checklist:** - [ ] Implements stated requirements - [ ] Handles specified edge cases - [ ] No scope creep (unexpected additions) - [ ] No missing functionality **Feedback at this stage:** - "This doesn't appear to handle the case when X is empty" - "The requirement specified Y, but this implements Z" - "This adds feature F which wasn't requested - is that intentional?" ### Stage 2: Correctness Next, verify the code works correctly. **Checklist:** - [ ] Logic is sound - [ ] No obvious bugs - [ ] Error paths are handled - [ ] No unfinished code (TODOs without tickets) **Feedback at this stage:** - "This will throw if `user` is null" - "The loop exits early before processing all items" - "What happens when the API call fails?" ### Stage 3: Code Quality Then, evaluate code quality and maintainability. **Checklist:** - [ ] Clear naming - [ ] Reasonable function/method length - [ ] No unnecessary complexity - [ ] Follows project conventions - [ ] Appropriate abstractions **Feedback at this stage:** - "Could