Maintaining code quality and TODOs turns out to be a surprisingly hard problem, but it's far more of a social / organisational one than technical, which is why technical tools don't solve it.

In my experience this kind of thing works only with the discipline and will to actually get to it, and that really depends on the project, team and management dynamic.

I've been receiving a "stale issue, closing soon" notification on an open source project every two months for over a year, which I dutifully bump and the issue continues to be studiously ignored. Much respect to that team, but the techno-fix of quarterly reminders are not addressing the core issue of missing will, process or personnel. It's a bit like setting a clock ahead in order to leave on time: the will to be on time is the driver, not the clock.

However, for those teams with the will and process to address old TODOs, seems like a nice reminder. I might use it!

It’s easy to get a team to make this 2nd nature and gets immediate debt in the backlog. It can of course still be ignored and unfinished for a long time still but no amount of automated nagging will change that in my experience

Example: https://github.com/lobsters/lobsters/commit/9e99fbf1d3cc441e...