tarn_impact
Identify which .tarn.yaml tests are most likely affected by changes to files, endpoints, or OpenAPI operations, with confidence tiers and run hints.
Instructions
Map a change (files / endpoints / openapi ops / git diff) to the .tarn.yaml tests it most likely affects, with confidence tiers and run hints. Read-only: no HTTP and no test execution. Equivalent to: tarn impact --format json.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | Absolute path to the project root. Defaults to the workspace root captured during MCP `initialize`, or the server process's current directory. | |
| diff | No | When true, run `git diff --name-only HEAD` under `cwd` and feed the result in as changed files. | |
| endpoints | No | Endpoints touched by the change. Each entry is either a `METHOD:/path` string or a `{method, path}` object. | |
| files | No | Changed source files as plain strings. | |
| min_confidence | No | Drop matches below this tier before returning. | |
| no_default_excludes | No | Disable the default discovery ignore rules (e.g. `.git`, `node_modules`). | |
| openapi_ops | No | OpenAPI `operationId`s whose behaviour changed. | |
| path | No | Restrict test discovery to this subpath (file or directory). Relative paths resolve against `cwd`. |