staleness_check
Compare findings against git history to detect stale code issues. Returns file status as current, modified, renamed, deleted, or unknown to show which findings need re-review.
Instructions
Check if findings are stale by comparing against git history.
Staleness is checked against each finding's NEWEST observation: a
deduplicated re-observation records its commit in the occurrence ring,
and that commit — not the frozen first-report reported_at_commit —
is what the file is compared from; findings with no ring fall back to
the first report. Each result carries checked_commit, the commit the
verdict was computed against.
Returns file_status for each finding:
current: file unchanged since finding was reported
modified: file changed but still exists
renamed: file was renamed/moved
deleted: file no longer exists
unknown: can't determine, with a
reasonnaming which question could not be answered — no provenance data, an unreachable commit, a path outside this repository's worktree, a path the reported commit never contained (a glob, free text, or a file added later), an empty or malformed value, a path that is neither a file nor a directory, or a git/stat call that failed
Args:
finding_id: Check a single finding (e.g. CB-1)
status: Filter by finding status (default: open)
category: Filter by category
file: Filter by file path (substring match)
resolve_anchors: Also resolve each finding's location anchor against HEAD, so a record says where the reported LINES are now and not only what became of the file. OFF by default: this query permits ten thousand rows and already spends git per file. Every record carries the cheap half of the summary either way — whether the card has an anchor at all.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file | No | ||
| status | No | ||
| category | No | ||
| finding_id | No | ||
| resolve_anchors | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||