Code Review
Use for quick self-review of small changes. For comprehensive review or cross-domain changes, dispatch @code-reviewer agent instead.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill code-reviewgit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/code-review ~/.claude/skills/code-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Review Review code for quality and compliance. Report findings. > **Announce:** "I'm using code-review to review these changes before commit." ## This Skill vs @code-reviewer Agent | Situation | Use | |-----------|-----| | Small change (< 100 lines) | This skill | | Single domain (DB only or frontend only) | This skill | | Quick sanity check before commit | This skill | | Large change (> 300 lines) | Dispatch `@code-reviewer` | | Cross-domain (DB + frontend) | Dispatch `@code-reviewer` | | Security audit needed | Dispatch `@code-reviewer` | | Need fresh eyes (you wrote the code) | Dispatch `@code-reviewer` | To dispatch: Load `subagent-workflow` skill first. ## Iron Law ``` REPORT FINDINGS - DO NOT FIX ``` Your job is to identify issues. The main agent decides what to fix. ## Review Checklist ### 1. Architecture Compliance **Database-First (from architecture rule):** - [ ] Business logic is in PostgreSQL, not frontend? - [ ] Frontend only calls `supabase.rpc()`, no direct queries? - [ ] No game logic, scoring, or calculations in frontend? **Source-Based Workflow:** - [ ] Database changes are in `supabase/db/`, not migrations? - [ ] Both source files AND migrations are included? **Security:** - [ ] RLS policies validate `auth.uid()`? - [ ] SECURITY DEFINER functions check permissions? - [ ] No sensitive data exposed in frontend state? ### 2. Spec Alignment Run `openspec list --specs` and check: - [ ] Does implementation match spec requirements?
Details
- Skill name
code-review- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/code-review/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Code Review skill do?
Use for quick self-review of small changes. For comprehensive review or cross-domain changes, dispatch @code-reviewer agent instead.
How do I install the Code Review skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Code Review popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Codebase Conventions
8Freddy-CHEN-ux/00_claude_skills
Load when starting work in 10x-Mapmaster or when unsure about project standards. Covers file organization, naming conventions, type constraints, SQL style, and project-specific limits (200-char descriptions, answer enums). Use to understand how the codebase is structured and what standards to follow.
Clean Code
5vnovakovits/claude-skills
Apply Clean Code principles by Robert C. Martin (Uncle Bob) when writing new code, refactoring existing code, or reviewing changes in any language. Covers meaningful names, small functions, comments, formatting, objects vs data structures, error handling, boundaries, unit tests, classes, systems, emergent design, concurrency, and code smells.
Codex
5bolasblack/claude-skills
OpenAI Codex second opinion via the codex CLI — three modes. Review: independent diff review with a pass/fail gate. Challenge: adversarial pass that tries to break the code. Consult: ask Codex anything, with session continuity for follow-ups. Use when the user says "codex review", "codex challenge", "ask codex", or wants a second opinion from Codex.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.