Original Reddit post

I found out yesterday that I’m the third most active GitHub user in Portugal. I wasn’t looking for it. I stumbled onto committers.top , scrolled the list, and there I was at number three. It took me a second to work out how that happened, because I haven’t been pulling late nights writing code. The reason is simple: I don’t write most of those commits. Claude Code does, and it runs mostly on its own across half a dozen of my open-source projects. Here’s the setup. Commands I don’t have to repeat I kept typing the same requests. Find a bug. Write a test. Clean up old branches. So I turned each one into a small command, just a Markdown file, and keep them in my own plugin marketplace so they work in every project I open. Every command does one thing, opens its own pull request, and reports back in a single line: either it did something, or there was nothing left to do. /bug-hunt fixes an open issue. /add-test writes a test. /improve-code does one safe refactor. /housekeeping deals with branches and dependency bumps. Two are specific to me: one reads the real errors off my production server and files them as bugs, and another checks what competitors are shipping and drops feature ideas into my backlog to look at later. Autopilot runs them for me I still had to choose which command to run, so I wrote one that chooses for me: /autopilot . I tag a command with a single line, autopilot: true , and it joins the rotation. Autopilot runs through them, reads each report, drops the ones with nothing left to do, and keeps going until the list is empty. It decides on its own and never stops to ask me. There’s almost nothing to it, and that’s the point. There’s no master list to keep in sync. A command opts in with one line, and autopilot finds it. The orchestrator only picks what runs next; each command does the actual work on its own. Tests find the bugs It leads with tests of every kind: unit, integration, end-to-end. And it writes them to break the code, not to confirm it. it works out what the code should do, then tries to prove that it doesn’t. A failing test isn’t a problem, it’s a lead. It writes the bug up as an issue, the fixing pass picks it up, fixes the cause, and locks it down with a regression test so it can’t come back. Find, file, fix. I restart it every hour Long sessions drift. The context fills up with old detail and the agent loses the thread. So I built ClaudeCodeCron precisely for this. It starts a fresh autopilot run every hour. Each run begins clean, with a short and predictable context. That keeps the decisions sharp, and it’s the main reason the cost stays low, because I’m not carrying an hour of history into every step. It’s not perfect. It picks the next job at random, there’s no spending cap, and it merges without me checking. All three are on my list to fix, starting with real prioritisation and a review step before anything lands. But having a set of projects that keep moving while I do something else has been worth it. None of the pieces are complicated. A handful of single-purpose commands, one that runs them in a loop, and an hourly restart. They’re easy enough to rebuild for your own setup. submitted by /u/DanielAPO

Originally posted by u/DanielAPO on r/ClaudeCode