Start background static checks
start_checksStart a project's static checks in a detached background process and receive a runId immediately. Poll for results later using get_check_results.
Instructions
Fire-and-forget: spawn a DETACHED background run of the project's static checks (syntax-check of changed .js/.mjs/.cjs via node --check, plus any configured commands — lint, a fast test subset, etc.) and return a runId IMMEDIATELY. Pure CPU, zero model tokens, never blocks — the runner survives this call and writes its results to /checks/.json. Scope it to a commit with revision (else it uses the last commit / dirty tree). Poll results later with get_check_results. commit_feature already starts checks automatically on every commit (checks.autoOnCommit); use this to run them on demand. Returns started:false with a reason when the project has no checks config and no package.json in its code repo.
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": {
"project": "<project>"
},
"name": "start_checks"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ticket | No | Ticket to associate the run with (so get_check_results can find it by ticket). | |
| project | Yes | ||
| revision | No | Commit hash to scope changed-file detection to (git show); defaults to the last commit / dirty tree. |