# Code Review

> Review code changes using parallel review agents. Use when reviewing PRs, recent commits, or uncommitted changes. Invoke with /code-review or when asked to review code. Use engineering-patterns for structural/module-depth findings and production-readiness for service/reliability risks. Use when this capability is needed.

- Skill: `tomevault-io/code-review-160` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/code-review-160`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/code-review-160/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/code-review-160

---


# Code Review

Review code changes by running three independent reviews in parallel, correlating findings by severity, then validating with an architecture-level review pass. Use provided user guidance to steer the review and focus on specific code paths, changes, or areas of concern.

## Workflow

1. **Determine scope** — what to review:
   - If PR number/URL provided: fetch with `gh pr view` / `gh pr diff`
   - If uncommitted changes exist: review those (`git diff HEAD`)
   - Otherwise: review last commit (`git show HEAD`)

2. **Run 3 independent reviews in parallel** — each gets the same diff but reviews independently, focusing on bugs, security, and structure. Each review outputs findings with severity, file path, line number, and suggested fix.

3. **Correlate findings** by severity:
   - **Critical** — Will cause data loss, security breach, or system failure
   - **High** — Likely to cause bugs in production
   - **Medium** — Could cause issues under certain conditions
   - **Low** — Minor improvements, best practices

4. **Architecture validation** — Send correlated findings to an architecture-level reviewer for a deep accuracy/correctness review. The reviewer evaluates each finding against surrounding code, subsystems, abstractions, and overall architecture. Apply any recommendations (upgrade, downgrade, or dismiss findings). **NEVER SKIP ARCHITECTURE REVIEW.**

5. **Structural and production lenses** — For structural concerns, use
   `engineering-patterns` vocabulary: module, interface, depth, shallow module,
   seam, adapter, locality, leverage, deletion test. For service, data, async,
   external dependency, or deployment concerns, use `production-readiness`.

6. **Output unified report** — deduplicated, grouped by severity, with file paths, line numbers, and suggested fixes.

## Usage

```
/code-review              # Review uncommitted changes or last commit
/code-review 123          # Review PR #123
/code-review --last 3     # Review last 3 commits
```

## Output Format

```markdown
## Code Review Summary

**Scope:** {uncommitted changes | PR #X | last N commits}
**Files reviewed:** {count}

### Critical Issues
- **[file:line]** Description. Fix: suggestion.

### High Priority
- **[file:line]** Description. Fix: suggestion.

### Medium Priority
- **[file:line]** Description. Fix: suggestion.

### Low Priority / Suggestions
- **[file:line]** Description.

### Summary
{1-2 sentences: overall assessment}
```

## Review Principles

- **Be certain** — Don't flag something unless you've investigated
- **Full context** — Read entire files, not just diffs
- **No style zealotry** — Focus on bugs, not preferences
- **Realistic scenarios** — Don't invent hypothetical edge cases
- **Matter-of-fact** — No flattery, no hedging
- **Structural clarity** — When structure is the issue, explain how it affects
  locality, leverage, test surface, or blast radius
- **Production behavior** — When code crosses a boundary, check timeout, retry,
  idempotency, observability, migration, and rollback behavior

---
> Source: [mukealicious/dotfiles](https://github.com/mukealicious/dotfiles) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-16 -->

