Code health
This codebase scores 4.7 out of 10 for code health, which we rate needs work. It also scores maintainability 4.7 and static performance 9.1 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 75 of 1,487 files are git hotspots, and they average 1.9 — which is where the fixes pay off most.
3 things worth doing in the week to Sep 13, the last indexed commit, 3 of them now.
Start breaking up handleUIControl (CCN 97, 180 lines): first lift lines 115-136
static/js/chatStream.js:115
handleUIControl changes often and has low measured test coverage; 1 file imports it, changed 4 times in 90 days.
Start breaking up function_call_to_tool_block (CCN 110, 196 lines): first lift lines 15...
src/tool_schemas.py:1538
function_call_to_tool_block has a change entropy finding, and part of it is duplicated, so splitting it also removes a copy; 10 files import it, changed 5 times in 90 days.
Start breaking up initializeEventListeners (CCN 397, 2,693 lines): first lift lines 277...
static/app.js:277
initializeEventListeners changes often and has low measured test coverage, and part of it is duplicated, so splitting it also removes a copy; 1 file imports it, changed 16 times in 90 days.
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.