What a change reaches, and what to run
godot_impactTrace edited files backward through the project graph to every affected scene, autoload, test, and scenario, then get the exact checks to run before declaring the work done.
Instructions
The blast radius of a change, offline: from the changed files (default: everything that differs from git HEAD, new files included; or files) backwards through the project's file graph (ext_resource, preload, class_name, includes, and paths the code loads later) to every scene that loads them, nearest first with the chain in between and the main scene marked; whether the change is global (an autoload or something an autoload loads, project.godot, a class_name many scripts use); the test files and saved scenarios that cover it; deleted files something still names; then the numbered checks to run for exactly this change (godot_review with the files, godot_check, the scenarios, the tests, the scene to play). Call it when you finished a set of edits, before you say the work is done: checking only the file you edited misses the scenes that instance it. Read-only.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "godot_impact"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ref | No | the commit to compare with when files is not given (default HEAD) | |
| path | No | project folder, or a file or folder inside it (relative to the server's folder; default: the current project) | |
| files | No | the changed res:// files (default: what differs from ref in git) | |
| detail | No | brief (capped lists) or full (everything); default full |