Audit a proposed implementation
auditChallenge proposed code changes for scope creep, rewrites, contract assumptions, security implications, error handling, and missing validation using supplied evidence.
Instructions
Challenge a proposed code change for scope creep, rewrites, contract assumptions, security implications, error handling, and missing validation.
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": {
"proposal": "<proposal>"
},
"name": "audit"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| evidence | No | Evidence establishing the problem or contract. | |
| proposal | Yes | Proposed implementation or change plan. | |
| sessionId | No | Optional bounded in-process session identifier. | |
| proposedChanges | No | Concrete, file-level changes to classify. | |
| reportedProblem | No | Observed bug or requirement the change is intended to address. |