I built a small tool that makes one cleanup commit at a time, keeps it only if tests pass, and moves on. The article is about how it grew from that basic loop into taste files, staged migrations, and a way to keep repos getting a little cleaner in the background.
Thank you for sharing, it is inspiring to see other's ideas. I sometimes use it to create projects that would be a nice to have, my latest project was a go project called hookguard, a go binary that enforces deterministic safety rules for AI coding agents.
Comments
I built a small tool that makes one cleanup commit at a time, keeps it only if tests pass, and moves on. The article is about how it grew from that basic loop into taste files, staged migrations, and a way to keep repos getting a little cleaner in the background.
https://github.com/bigH/continuous-refactoring
Thank you for sharing, it is inspiring to see other's ideas. I sometimes use it to create projects that would be a nice to have, my latest project was a go project called hookguard, a go binary that enforces deterministic safety rules for AI coding agents.