Installs into .claude/skills of the current project.
Are you the author of Code Review 142?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/david-li0406-code-review-142)
---
name: code-review
description: Audits code for errors, security issues, and alignment with project rules.
---
# Code Review Standards
> **IMPORTANT**: ASSUME the code has already passed tsc and eslint. Do not waste tokens checking for missing semicolons or any types. Focus on logic, user experience, and architecture.
## 1. The "North Star" Check
- **Verification**: Does the code actually fulfill the requirements in `specs/issue_*.md` (or `specs/active_PRD.md`)?
- **Premium Polish**: Does the code include the required premium indicators (Haptics, Skeletons, Loading states) mentioned in the PRD or Project Rules?
- **Visual Uniformity**: Check for inconsistent design tokens (e.g., mismatched backgrounds or fonts across screens). A visual refactor is only complete when applied globally.
- **Scope Creep**: Did the code add unnecessary features not requested in the PRD?
## 2. Technical Compliance
- **Stack Alignment**: Does the code match the tools defined in `specs/tech-stack.md`? (e.g., Don't use `axios` if we decided on `fetch`).
- **Testing**:
- Do tests exist for the new code?
- Do the tests follow the `testing-standards` skill?
- **Types/Safety**:
- Are errors handled gracefully (try/catch)?
## 3. Security & Cleanliness
- **Secrets**: Are there any hardcoded API keys or passwords? (FLAG IMMEDIATELY).
- **Console Logs**: Are there leftover `console.log` statements?
- **Comments**: Are complex logic blocks explained with comments?
## 4. Logic & Architecture
- **DRY Types (The "Single Source" Rule)**: Never duplicate complex type or interface definitions. If a data structure is used in more than one layer (e.g., Service AND Hook), it MUST be defined in `types/schema.ts` and imported.
- **Error Handling**: Every network or DB call MUST have a `try/catch` block or a defined error state in a TanStack query.
## How to Report
- **Review Archival**: Every finalized review MUST be saved to `specs/reviews/[feature_name]_review.md`.
- **Pass**: "✅ Code looks good and meets all standards."
- **Fail**: List the specific file, line number, and the violation.
- **Fix Suggestion**: Provide the exact code block to fix the issue.
