I had been thinking about what to actually do with Claude Code's Routines feature for a while.
It runs prompts in the cloud on a schedule, which sounds useful, but what's actually worth firing every couple of hours?
What I landed on is performance tuning .
"Did it get faster?" is a question you can answer with numbers, so as long as you have a benchmark in place, the rest can be handed off to an AI. If you have tests, regressions get caught for you. The work happens on a branch, so nothing leaks into main. And a lot of perf wins are "patterned" changes — swapping a dependency, lazy-loading something, cutting an I/O — that don't really need much creative design.
I tried this on Repomix , the CLI I maintain, and the runtime ended up roughly 2.4x faster .
v1.14.0 release notes
It's reproducible enough now that I think it's worth sharing.…