← ClaudeAtlas

code-reviewlisted

10-point code review checklist covering correctness, tests, error handling, type hints, naming, security, and performance. Use when reviewing PRs or evaluating code quality. TRIGGER when: code review, PR review, review checklist, code quality check. DO NOT TRIGGER when: writing new code, debugging, refactoring without review context.
akaszubski/autonomous-dev · ★ 29 · Code & Development · score 68
Install: claude install-skill akaszubski/autonomous-dev
# Code Review Enforcement Skill Ensures every code review is thorough, consistent, and produces actionable feedback. Used by the reviewer agent. ## 10-Point Review Checklist Every review MUST evaluate all 10 items. No shortcuts. ### 1. Correctness - Does the code do what the ticket/plan requires? - Are edge cases handled (empty input, None, boundary values)? - Are return types consistent with declarations? ### 2. Test Coverage - Do tests exist for new/changed code? - Do ALL tests pass (100%, not "most")? - Are edge cases and error paths tested? ### 3. Error Handling - Are exceptions specific (not bare `except:`)? - Do error messages include context (what failed, what was expected)? - Is there graceful degradation where appropriate? ### 4. Type Hints on Public APIs - All public functions have parameter and return type annotations? - Complex types use `Optional`, `Union`, `List`, `Dict` correctly? ### 5. Naming Conventions - Variables/functions: `snake_case` - Classes: `PascalCase` - Constants: `UPPER_SNAKE_CASE` - Names are descriptive (no single-letter except loop vars) ### 6. Security - No hardcoded secrets, API keys, or passwords - No bare `except:` that swallows errors silently - SQL queries use parameterized statements - User input is validated before use ### 7. Style Compliance - Code is formatted with black (100 char line length) - Imports sorted with isort - No unused imports or variables ### 8. Documentation - Public APIs have Google-style docstrings - Comp