# Code Review

Use when receiving code review feedback (especially if unclear or technically...

- Repository: https://github.com/mrgoonie/claudekit-skills (2229 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-04-03
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add mrgoonie/claudekit-skills --skill code-review -g -a claude-code -y`
Codex: `npx skills add mrgoonie/claudekit-skills --skill code-review -g -a codex -y`
Cursor: `npx skills add mrgoonie/claudekit-skills --skill code-review -g -a cursor -y`
Gemini CLI: `npx skills add mrgoonie/claudekit-skills --skill code-review -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add mrgoonie/claudekit-skills`

## Description

Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Code Review

Guide proper code review practices emphasizing technical rigor, evidence-based claims, and verification over performative responses.

## Overview

Code review requires three distinct practices:

1. **Receiving feedback** - Technical evaluation over performative agreement
2. **Requesting reviews** - Systematic review via code-reviewer subagent
3. **Verification gates** - Evidence before any completion claims

Each practice has specific triggers and protocols detailed in reference files.

## Core Principle

**Technical correctness over social comfort.** Verify before implementing. Ask before assuming. Evidence before claims.

## When to Use This Skill

### Receiving Feedback
Trigger when:
- Receiving code review comments from any source
- Feedback seems unclear or technically questionable
- Multiple review items need prioritization
- External reviewer lacks full context
- Suggestion conflicts with existing decisions

**Reference:** `references/code-review-reception.md`

### Requesting Review
Trigger when:
- Completing tasks in subagent-driven development (after EACH task)
- Finishing major features or refactors
- Before merging to main branch
- Stuck and need fresh perspective
- After fixing complex bugs

**Reference:** `references/requesting-code-review.md`

### Verification Gates
Trigger when:
- About to claim tests pass, build succeeds, or work is complete
- Before committing, pushing, or creating PRs
- Moving to next task
- Any statement suggesting success/completion
- Expressing satisfaction with work

**Reference:** `references/verification-before-completion.md`

## Quick Decision Tree

The rest: https://github.com/mrgoonie/claudekit-skills/blob/HEAD/.claude/skills/code-review/SKILL.md