review

name	review
description	Use for focused review of a Neva pull request, branch, diff, or patch.

Review

Use this skill for high-signal review of a code change. The change may be a pull request, a branch, a local diff, or a patch. The goal is to publish only required changes or blocking questions.

Workflow

1. Read the diff and required repository context:
   • AGENTS.md
   • canonical documentation named by its change-routing table
2. Review from four focused perspectives:
   • correctness: references/review-correctness.md
   • style and readability: docs/user/style_guide.md for Neva code, plus references/review-readability.md
   • performance: references/review-performance.md
   • security: references/review-security.md
3. Use subagents when available and useful. If subagent tooling is unavailable, run the four review passes yourself.
4. Deduplicate overlapping findings.
5. Output only actionable findings and blocking questions. If there are no meaningful findings, say that clearly.

Output Contract

• Findings first, ordered by severity.
• Include file/line references whenever possible.
• Do not include praise, strengths, or broad summary prose before findings.
• Report clear violations of docs/user/style_guide.md for Neva code. Do not report subjective style preferences.