validate_scope
Recommends relevant validation checks and commands after code edits, using known changed files when provided and inferring scope from the task otherwise.
Instructions
After edit_scope, recommend the most relevant validation checks and commands. Pass files when you already know what changed; they take precedence over task inference.
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": {
"task": "<task>"
},
"name": "validate_scope"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| root | No | Absolute project root. Omit only where this session started; required elsewhere and on every subagent call. | |
| task | Yes | Task description or intended change. | |
| files | No | Files already changed or known to be in scope. These take precedence over task inference. | |
| format | No | Return plain text or structured JSON. Default: text. | |
| max_files | No | Maximum files to inspect when building validation guidance. Default: 5. |