I have a static analysis and refactoring tool that does wonders to identify duplication and poor architecture patterns and provide a roadmap for agents to fix the issues. It's like magic, just point it at your codebase then tell the agent to grind away at the output (making sure to come up for air and rerun tests regularly) and it'll go for hours.

▲

lenerdenator 3 days ago | parent [-]

What's it called?

▲

CuriouslyC 3 days ago | parent [-]

Official release is tomorrow, I'm just doing final release prep cleanup and getting the product page in order, but the crate/brew formula is in decent shape, just missing some features I'll be shipping soon. https://github.com/sibyllinesoft/valknut if you want to jump the line though.

▲

svieira 3 days ago | parent [-]

A quick pass through this repository validates that there is a lot of tech debt in this code too. For a very simple example, consider that the analysis code is doing string searches to attempt to detect various syntatic constructs. https://github.com/sibyllinesoft/valknut/blob/aaf2b818a97b8d...

	▲	CuriouslyC 3 days ago \| parent [-]
		I realize, my marketing page even puts it front and center (I use the tool to analyze the tool, yay dogfood). I'm compute limited at the moment and I don't have cycles to burn refactoring this code base since it's pretty close to feature complete right now, I need to put all my compute towards finishing up development of a few projects I'm trying to ship this week, and some exhaustive bechmark matrixes. Regarding that string search, you really have to fight Claude to get it to use tree sitter consistently, I have to do a search through my codebase to build an audit list for this stuff.