"I just paste tickets into Claude Code and hang out."
That's the reality of some software development these days.
As a product manager, I don't really care. Did we hit our sprint goals? Is the software stable? Did we build the right thing?
That's what I care about.
Doesn't matter to me who or how the code is built.
So we're pushing boundaries. We're automating PRs with Claude Code.
Initially it was terrible.
Claude would introduce thousand line code changes that no human could review. It slowed us down and was more work than it was worth.
So we tweaked the approach. Defined stricter PR rules in our claude.md, started tagging smaller tickets during backlog planning that Claude could one shot. And invested in testing.
It's made a huge difference. Now PRs are quick to review and can be cleaned up in a couple minutes.
Engineers are spending less time on tech debt and bug fixes. They're focused on architecture, tech strategy, and feature validation.
I don't think the question is should your team automate PRs with Claude?
The question is have you taken the time to set it up to actually work.