---
name: code-review
description: "Find actionable defects in a change without flooding the author with style opinions."
license: CC0-1.0
metadata:
  author: "SI Editorial"
  version: "1"
---

# Review for correctness and risk

## When to use
Find actionable defects in a change without flooding the author with style opinions.

## Workflow
1. Read the change and its surrounding call sites.
2. Trace concrete failing inputs, permission checks, cleanup, retries, and concurrency.
3. Report only supported findings with file locations, user impact, and a minimal correction.
4. If no defect is found, state what was checked and what remains unverified.

## Boundaries
Use only tools and data authorized for the task. Ask for missing requirements when they affect the result. Report what you verified and what you could not verify.

## Try it
Review this pull request for authorization and duplicate-write bugs.

## Success looks like
Prioritized findings grounded in a reproducible failure path.