If You Can't Own the PR, Please Don't Open One
A pull request should be opened by the person who can explain the change, assess its risk, and handle the fallout if it goes wrong.
Thoughts on automation, developer tools, and software engineering.
A pull request should be opened by the person who can explain the change, assess its risk, and handle the fallout if it goes wrong.
Code generation keeps getting cheaper. But someone still has to read it. Turns out the highest-leverage skill in 2026 might not be writing code - it's deciding whether it should ship.
I'm guilty of every bad commit message sin in the book. So I built a Claude Code skill that writes them better than I ever did.
I was the PR template guy. Now I've automated it. Anyone can get a well-structured PR without thinking about it. The skill I was known for is now... a prompt?