Reason about the task
Useful code begins with understanding the problem and its constraints. Missing requirements and ambiguous behavior should be surfaced before they become implementation choices.
Work with existing context
Real software has interfaces, conventions, dependencies, and history. Evaluation should ask whether a proposed change fits the surrounding system, not only whether it works in isolation.
Verify the outcome
Execution, targeted tests, and review offer different forms of evidence. A proposed patch is not a successful result until its behavior has been checked in the intended environment.
A question to explore
Explain this function, identify edge cases, and propose a focused change with a verification plan.
This example illustrates a task direction. It is not a recorded demonstration or a claim of verified performance.
What to evaluate
Repository context, hidden edge cases, insecure assumptions, unintended side effects, and whether proposed tests actually validate the task.
Explore the evaluation approach