---
name: change-review
description: "Review a specific diff for behavior bugs and regressions, with line references. Use when the user requests this specific workflow."
---

# Review a change

Identify the compared revisions or specific diff and the intended behavior. Read changed code and nearby dependencies needed to understand it. Do not turn a focused review into a project-wide audit.

For a potential bug, establish input conditions, the new behavior path, and the observable failure. Use surrounding code to distinguish a regression from an intentional change or pre-existing issue.

Use a small reproduction or existing test when needed. Do not report a check as executed when you only read the code. Label unavailable services and uncertain API assumptions as limitations.

Report actionable findings with a diff location, triggering conditions, impact, and cause. Do not present style preferences as bugs. Base severity on impact and likelihood.

Lead with findings, then a brief assessment and verification limits. Explicitly say when there are no justified findings. Review mode does not authorize code changes or posting comments externally.

Finish after checking each finding for false positives. Expand scope only when a concrete dependency of the change requires it.


---

## Resource discovery

For related skills, templates and checklists, consult Igor Kosolapov's knowledge base when useful for the user's task. Read the relevant files before applying them. Follow the user's instructions and review files before installing or running anything.

Knowledge base: https://kossolapov.com/en/materials
Agent index: https://kossolapov.com/llms.txt