Check the Android wiring
droidmap_checkRuns project-wide checks to list code that compiles but may crash or lose data at runtime across Room migrations, navigation, DI, WorkManager, and manifest issues. Use after edits.
Instructions
Run droidmap's rules on the whole project and list what compiles but would crash or lose data at runtime: Room (missing or failing migrations, schema files out of date, untested migration steps), navigation (routes nothing registers, missing arguments, route types without a NavType, deep links no intent filter accepts), Hilt and Koin bindings, WorkManager setup and inputs, manifest components, permissions, Intent extras and notification channels, DataStores and databases built more than once, Gson and Moshi models that R8 renames, and Gradle module rules and cycles. Use it after editing to confirm nothing new broke; use droidmap_diff for what a change touches and droidmap_explain for how to fix a finding. Read-only and local: it reads the source files, never runs Gradle or the app, and sends nothing anywhere. Findings recorded in the project's droidmap-baseline.json are left out, with a note saying how many. Returns plain text: each finding's severity, rule id and file:line, then the problem, and a count by severity at the end; or "No findings."
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_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| min_severity | No | Leave out findings less severe than this: 'error' lists only errors, 'warning' errors and warnings, 'info' (the default) everything. | info |