sumo_qa_analyze_diff_impact
Maps changed files to their likely tests, identifies risk surface (uncovered changes), one-hop affected nodes, and unmapped files from a diff against a base ref.
Instructions
Map a set of changed files onto the repo-map to report which tests likely exercise them, which changed sources have no mapped test (the risk surface), one-hop affected nodes, unmapped files, and whether the map is stale relative to HEAD.
Common natural-language phrasings that map to this tool: "what does this diff affect", "which tests cover my changes", "what's the risk surface of this branch", "what should I re-test after these edits", "analyse the impact of the changes against main".
root is the repository. Supply changed_files (repo-relative
paths) OR base_ref (any git ref; changed files are the diff against
the merge-base of base_ref and HEAD, so changes that landed on the
base after the branch diverged don't leak in). The repo-map is read
from artifact_path when present and falls back to a live scan
otherwise; an artifact for a different project root is ignored. On the
first run of an unmapped repo the live scan is persisted to
artifact_path (reported as persisted_map_path) unless
artifact_path is None. write_overlay writes
.sumo-qa/diff-impact.json under root. When test files exist but
the map has no likely_tests edges, probable_mapping_gap flags the
risk surface as a missed-convention gap rather than true zero coverage.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| root | Yes | ||
| base_ref | No | ||
| artifact_path | No | .sumo-qa/repo-map.json | |
| changed_files | No | ||
| write_overlay | No |