What a change touches
droidmap_diffMaps code changes since a git ref onto the project graph to show changed and removed declarations, affected dependents, covering tests, and findings so you can update code and run the right tests.
Instructions
Map a code change onto the graph: the declarations whose lines changed since a git ref (by default the uncommitted changes, new files included), the ones removed, everything that depends on them (screens, destinations, ViewModels, Room, bindings, modules), the test classes whose calls reach the changed code, and the findings in the changed files, including those only a comparison shows (a shipped Room schema or a stored enum constant changed, a Worker renamed). Use it after editing, to see what else to update and which tests to run; use droidmap_impact before editing. Read-only: it runs git diff and reads the source files, never runs Gradle, and changes nothing; the project must be in a git repository. Returns plain text in sections: Changed, Removed, Affected (grouped by kind), Tests that cover it, and Findings in the changed files.
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": "droidmap_diff"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| base | No | The git ref to compare with: a branch, tag or commit, such as 'main', 'origin/main' or 'v1.2.0'. The default, 'HEAD', compares the working tree with the last commit, so it shows the uncommitted changes. With a branch, droidmap compares with the point where the current branch left it. | HEAD |
| depth | No | How many dependency steps to follow outwards: 1 lists only direct users; the default, 4, is enough for most changes. |