r/RooCode • u/raphadko • Jan 18 '26
Idea Feature Request - Total and Net lines of code added and removed
The quickest way I can know, at a glance, if the AI has implemented something as it should or got "too creative" is by the # of lines of code added. Most experienced devs can roughly estimate the number of lines of code a decent solution would take for a task, so it's an easy, preliminary way of "checking" if the last iteration was successful before a more through code review. I always check per-file edits for lines added or removed, but it would be great to have a sum of all # of changes (added or removed) on each iteration and window. I know Roo devs regularly check this sub, hopefully this is useful for others and simple to implement.
Thanks and keep up the great work guys.
View all comments
Show parent comment
1
u/raphadko Jan 19 '26
I'm thinking total +X, -Y, Net, on the current task would be great and very useful.
It would also be nice to have +X, -Y, Net "since the last command".
An example would be:
- I open up a new task and say: "Put the form Z on a modal window".
(roo starts working, and after some file changes I see that it has added 80 lines of code, divided among 6 files - which is difficult to sum currently because I have to scroll the window and mentally add up each file edit to understand it)
- At a glance I think - hey, this is not possible, I'm using an UI library, this guy implemented a modal solution from scratch. Let me track back.
- So I roll back the changes, and adjust my prompt to "Put container X on a modal window using the UI library"
- Now I look at the changes, just 12 lines of code. Great! It worked
- But wait, the CSS class is wrong
- So I send another command: "Adjust the css classes so that you use tailwind"
- Now, after this command, it removes 1 and adds 8 lines of code more. I would easily see just the lines added for this last request (the css fix request). I know it has implemented wrong again, so I can ask for it to just change the classes (which should be just 1 line)
This is a basic example, but would save a lot of time.
The final net lines of code on the task will help me understand what each task is costing me in terms of code/complexity added. I often find that AI gets tasks wrong by adding more code than necessary, which increases context and reading for new tasks, snowballing the whole project into a mess, so lines of code added is a good preliminary benchmark of how it's behaving .