- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper adds an automatic check after each code edit and tells the agent which functions have cyclomatic complexity above 6 and which changed lines were not run by tests. It is tested with DeepSeek on SlopCodeBench, showing that complexity feedback lowers compared with reminders alone. No statistically significant gain in passing hidden tests is shown by using this method, so that whether the method is really helpful remains unknown.
Critical strengths
None
Critical weaknesses
- The main contribution looks just like adding a skill that asks the agent to check complexity and test coverage. The paper compares with reminders alone, but not with an agent loop with a skill that tells the agent to run the same tools, so I do not see enough novelty here.
- Asking the agent to lower function complexity makes it split functions. On Commit0, putting the single-use helper functions back together removes most of the score gain, and the paper shows no clear gain in correctness or in the cost of later edits.
Questions for authors
- Would adding a skill that tells the agent to run these same tools and fix the reported issues before finishing work to popular agent loops (claude code, codex, or opencode) just as well under the same budget?
- Does the resulting code make later changes cheaper or less likely to break things, or is the main benefit just a lower complexity score?