Oh, I'm sure you wouldn't love to look at it. :) It's not exactly messy, AIs are good at keeping things tidy, but everything about it is ad-hoc. It was never intended to be seen my another mortal's eyes than mine. I don't think there are any API keys or other secrets tucked away in the repo's history but I'd rather not risk it.

Your mess of files is different from my mess of files and the things you'd want to do with them is different from what my code does, I'd suggest getting your own agent on the task from a blank slate. That's the whole point I've been arguing here, that coding agents make these kind of bespoke "home-cooked" applications a lot easier to spin up.

As I recall, my first steps weren't even to have the coding agent write code. I explained my general goal and told it to look through the folders itself to see what work it thought needed doing. That was how I learned that almost all the cover art I'd downloaded from Udio years ago was actually AVIF format that had just been given the file extension JPG, for example - I didn't even know that needed to be fixed.

Make sure you back up your files before turning an AI loose on them, of course. Mine's been very well behaved (I warned it that avoiding data loss was the most important priority) but mistakes can be made.