- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper builds a requirement-code correspondence before each round of code modification. It uses repository dependencies and PageRank to describe the code structure, then asks an LLM to identify the target files and potentially affected prior components from the current and earlier requirements. On EvoCode-Bench, the method increases per-round reward from 44.65% to 54.87% with Claude Code running DeepSeek-V4-Pro.
Critical strengths
The method is being added to an existing coding agent, so this comparison gives some evidence that explicitly tracking requirements can help even when the agent already has tools to explore the repository. The results show that the average reward can increase 10% with Claude Code, which is useful.
Critical weaknesses
- The paper discusses related methods such as TraceDev, CodexGraph, and LocAgent, but does not compare with them. I would like to understand what is new in the requirement-code correspondence, beyond combining a repository graph with records of earlier requirements.
- The experiments compare the full method with the original agent, but do not test whether prior requirement records or an extra planning step would be enough.
Questions for authors
- Have you compared RepoTrace with the simpler baseline that gives the agent the same prior requirement records and asking it to plan before editing? I would like to know how much the repository structure analysis adds to that simpler setup.
- Which part of the requirement-code correspondence differs from the tracing and graph-based methods discussed in Section 3? Could you point to a comparison or ablation that shows why this difference matters?