Code Review

Review the requested change set against its intended behavior. Prioritize defects and release risk over style commentary.

Boundary

Review only the requested diff, patch, files, or comparison range, plus the surrounding code needed to validate behavior. Do not modify code unless the user explicitly asks for fixes.

Identify the language, framework, and relevant versions before reviewing framework-dependent behavior. Apply framework-specific review guidance whenever the change runs inside a framework. If that guidance or the required version context is unavailable, limit the review to demonstrated language-neutral defects and do not approve framework-dependent behavior.

Use other specialist guidance when the main question is narrower, such as algorithmic complexity, test quality, infrastructure, or privacy.

Required Context

Establish: