Skip to content
Back to skills

Code Review 69

ASecurity

Review code for quality, security, and best practices. Use when reviewing recent changes, PRs, or checking code quality. Proactively use after significant code modifications.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
code-qualitytypescriptgobashsqltestingcode-reviewapidatabasesecurity

Works with

  • api

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill code-review-69 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Review 69?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Review 69
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-code-review-69/badge)](https://www.skillsdirectory.com/skills/david-li0406-code-review-69)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-review
description: Review code for quality, security, and best practices. Use when reviewing recent changes, PRs, or checking code quality. Proactively use after significant code modifications.
allowed-tools: Read, Grep, Glob, Bash
---

# Code Review

Comprehensive code review following project standards.

## Review Checklist

### Code Quality
- Clear naming conventions
- No code duplication
- Proper error handling with `{ success, error }` pattern
- TypeScript types explicit (no `any`)

### Project Patterns
- Uses hooks for Supabase queries (not direct queries in components)
- Services return `{ success, data?, error? }`
- AI calls go through `aiGatewayService.ts`
- Data transforms follow 4-layer schema (Raw → Parsed → Database → Display)

### Security
- No hardcoded secrets or API keys
- Input validation on external data
- SQL injection prevention
- XSS protection

### Testing
- E2E tests use `?e2e=1` for auth bypass
- Schema transformers have validation tests

## Output Format

For each finding:
- **Severity**: Critical / Warning / Suggestion
- **File:Line**: Location
- **Issue**: Description
- **Fix**: Recommended solution

## Trigger Phrases

- "review my changes"
- "code review"
- "check this code"
- "/review"

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…