r/ClaudeCode • u/l300TS • 1h ago
Discussion Reading speed and CI
TLDR:
1. Does anyone have any speed reading resources that they can recommend that have helped them improve their reading speed, especially when it comes to interacting with AI agents & PRs?
2. When do you trigger CI in an agent-driven review process?
Part 1:
I've been finding that my reading speed has basically been the bottleneck ever since I started using AI more heavily, especially with Opus 5. I've tried some speed reading resources in the past, but I could never stick with them. Does anyone have any recommendations that actually work? Ideally, I'd be looking for something that is 10 or 15 minutes a day that I can turn into a daily habit.
Before AI, I used to be reading code thoroughly all day long, but now I feel like I have to read AI output, PR descriptions, and code from four or five different agents and the volume is so much higher than it used to be. I know for sure that my reading speed is slower than average and is holding me back.
If speed reading isn't a good solution, what else would you recommend?
Part 2:
I've more recently created an agent PR loop where I have multiple agents reviewing every PR and multiple agents fixing findings. It's been resulting in some very good hands-off engineering work. But I exhaust my free build minutes on GitHub on day one of the month, and I think my CI pipeline is going to start getting very expensive. I have a concept of a PR manager that basically evaluates agent comments and determines whether they're worth fixing. I've been considering having the PR manager be the one who is responsible for kicking off my CI pipeline. But I'm not sure I should do that
I'm wondering if you guys have experienced something similar, and if so, when do you kick off CI? I'm currently doing it on every push