Review a code change
Find actionable correctness and security problems in a change.
What to have ready
- The change or diff, its intended behavior and relevant project context.
- Build/test instructions where available; disclose missing access instead of guessing.
A task to start with
Find a concrete correctness problem before using a code change.
An illustrative request
Use the code-review workflow on this diff and its intended behavior. Focus on realistic failures, cite affected code and suggest a focused way to verify each finding. Keep missing context and uncertainty visible.
How to check the result
Locate each finding in the actual change and reproduce important failures where possible; no findings is not a guarantee.
This preview explains the task and checking approach. It is not a demonstrated customer outcome or a guarantee.
See what a useful orientation looks like.
The free worked example includes source files, an actual entry-point trace and executed checks you can compare with the code.
Open the worked example