buggy_repair
Prove a defect in a Python function, generate candidate fixes and verify each by execution, returning a verified, overfit or rejected verdict with evidence plus a patch to review.
Instructions
Prove a defect and then propose fixes, each verified by execution: does it parse, does the proven trigger stop failing, does anything that worked change, and do other inputs of the same shape get fixed too. Verdicts are 'verified', 'overfit' or 'rejected', each with the evidence. Nothing is written to the file. Show the user a verified patch and let them decide; apply it yourself only if they agree.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"function": "<function>",
"file": "<file>"
},
"name": "buggy_repair"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file | Yes | Path to the Python file, absolute or relative to cwd. | |
| budget | No | Inputs to execute before giving up. Default 300. | |
| timeout | No | Seconds allowed per call. Default 2. | |
| function | Yes | Function name. Use a dotted name for a class member, e.g. 'Cart.total'. | |
| preconditions | No | Preconditions as PYTHON expressions over the parameter names, e.g. 'budget > 0'. For an instance method the constructor's parameters are in scope too. Inputs that fail these are skipped, so they also decide which inputs a fix is allowed to change. | |
| postconditions | No | Postconditions as PYTHON expressions. 'result' is the return value, e.g. 'result >= 0'. A condition that cannot be evaluated is reported as a warning, never silently skipped. |