How a team keeps understanding the code its agents write
-
A merged pull request is not evidence that anyone understood it
Every ownership tool you have rests on one assumption, that whoever wrote the code understands it. Agents broke that assumption, and the honest response is to stop scoring people by it.
Read → -
Most of what your agent built has no "why", because there never was one
We extract the reasoning behind agent-written changes and refuse to invent it. Measured on our own repo, 62 percent of decisions carry no alternative and no trade-off. The reasoning was not lost. It never formed.
Read → -
How to find out who on your team actually understands each part of the codebase
Git history tells you who worked where. It stops telling you who understands what the moment agents write the code. A method for building the honest picture, area by area, without quizzing anyone.
Read → -
I keep approving agent PRs I never actually reasoned about
A Claude Code hook that makes the same agent write down why it opened a PR — Decisions, Trade-offs, Assumptions, Limitations. Local, MIT, nothing uploaded.
Read →