process · two-phase-call-graph-search-files-broad-then TEC-0062 · proposed

Two-phase call-graph search, files broad then functions deep

Start from files the issue mentions, build a module-level call graph dynamically and explore it broadly to pick files, then expand only the chosen files into a function call graph and search it iteratively, with the graph structure steering

Proposed. Filed by the drafting stage because a paper introduces or tests it. Nobody has vouched for it. The claim drafted from that paper is its first evidence, and what the paper used to validate it is in that claim’s source note. Say whether it held up for you, below.

Start from files the issue mentions, build a module-level call graph dynamically and explore it broadly to pick files, then expand only the chosen files into a function call graph and search it iteratively, with the graph structure steering Filed by the drafting stage from Issue Localization via LLM-Driven Iterative Code Graph Searching (2503.22424) with status proposed: the paper introduces or tests it, and the claim drafted from the paper is its first evidence. The paper validated it by: Top-1 file and function localization accuracy on SWE-bench Lite and Verified against Agentless, LocAgent-style and other open localizers using the same open models; resolve rate of Agentless with and without its locations; ablations of each phase.. Nobody has vouched for it; add support or contest it on this page.

Addresses: Finding what matters in a large codebase

Does it work?

nothing measured0 supporting · 0 contesting sources

Efficacy claims — what this technique actually moves, under which conditions, and whether that has been contested.

No efficacy claim filed yet. The technique is catalogued; whether it moves the capability, and when, is a separate assertion that needs its own sources.

No search recorded either, so this says nothing about the literature — only that nobody has looked here yet.

Code

No repository linked yet. Contribute one.

Sources

Either way, bring evidence: a link, or what you saw.

Whether a technique works is a claim. What you file here becomes a claim about this technique under the capability it addresses, with your evidence as its source, and moves the standing above the same way a paper would.