[callgraph]
Resolves changed line ranges to the declarations containing them, with symbol keys and a change classification. Start a review here.
Review starts from a diff, but every analysis tool starts from a symbol. This closes that gap in one call.
An agent would otherwise guess which identifiers in a hunk are the changed declarations, then resolve them one at a time. The guess is wrong whenever the enclosing declaration is not in the diff context, and the round trips grow with the size of the change.
Try it locally in the Glider playground
| Name | Type | Required | Description |
|---|---|---|---|
| hunks | json | Yes | Changed ranges. Each carries beforePath, beforeRange, afterPath and afterRange. Both paths are nullable, and both are carried so a rename stays one result. |
| beforeFiles | json | No | Prior text of each changed file. Required to classify a modification; a pure addition needs none. |
| pathStyle | string | No | absolute or relative. Relative paths resolve against the solution root. |
| skip | number | No | Number of declarations to skip. |
| take | number | No | Maximum declarations to return. |
Resolve a review hunk to the declaration it changed
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "changed_symbols",
"arguments": {
"hunks": [
{
"beforePath": "src/Orders/OrderService.cs",
"beforeRange": {
"startLine": 42,
"endLine": 44
},
"afterPath": "src/Orders/OrderService.cs",
"afterRange": {
"startLine": 42,
"endLine": 47
}
}
],
"beforeFiles": [
{
"path": "src/Orders/OrderService.cs",
"content": "// previous contents"
}
]
}
}
}Returns the declarations that contain the changed lines. Each carries its kind and its span on every side that exists. Each carries a symbol key where one resolves. Each is classified as added, removed, signature-changed, body-only, or unknown. A changed line belongs to the innermost declaration containing it. The nearest externally addressable ancestor comes with it when the two differ. The whole ancestor chain never does. A local function reports no key of its own, because impact tools cannot resolve one; use its ancestor instead. Totals and the classification breakdown cover the diff before paging. One call therefore carries the complete summary, and only the detail list pages. The completeness block reports what the answer left out. It names files in unsupported languages and hunks that matched no declaration. signature-changed against body-only is API-compatibility metadata and nothing more. A body-only change cannot break a caller at compile time. It can still change behaviour, so never skip behavioural review on it. Never prune on unknown. This build takes explicit hunks rather than a git range.