# code-review

> Systematic multi-perspective code review with consistent quality gates.

- Author: nth5693
- Repository: nth5693/gemini-kit
- Version: 20260122213235
- Stars: 181
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/nth5693/gemini-kit
- Web: https://mule.run/skillshub/@@nth5693/gemini-kit~code-review:20260122213235

---

---
name: code-review
description: Systematic multi-perspective code review with consistent quality gates.
last_updated: 2025-12-20
---

# Code Review Skill

## Overview

A systematic approach to code review that moves beyond "it looks good" to rigorous quality verification. This skill provides specific checklists and procedures for different review types.

## When To Use

- **Self-Review**: Before submitting a PR or finishing `/work`
- **Peer Review**: When reviewing another agent's or human's code (`/resolve_pr`)
- **Plan Review**: When validating an implementation plan (`/plan_review`)

## Instrumentation

```bash
# Log usage when using this skill
./scripts/log-skill.sh "code-review" "manual" "$$"
```

## What do you want to do?

1. **Security Review** (Auth, RLS, Input) → `workflows/security-pass.md`
2. **Performance Review** (Database, Re-renders) → `workflows/performance-pass.md`
3. **Architecture Review** (State, Data Flow) → `workflows/architecture-pass.md`
4. **General Quality Check** → `checklists/pre-merge.md`

## Key Principles

- **Review in Passes**: Don't check everything at once. Do a security pass, then a performance pass, etc.
- **Reference Patterns**: Always check against `docs/solutions/patterns/critical-patterns.md`.
- **Verify, Don't Guess**: If you see a potential issue, verify it with a quick test or script.