|
I think when you want to truly understand how something works, you either reverse-engineer the thing, or you participate in its making, or at least, understand the reasoning behind the build. Reading the documentation is not enough – you need to see how the thing was made, why certain decisions were made, what trade-offs were accepted, and what assumptions were made. I don't really think it is possible to sustainably scale automated agentic end-to-end development without reviewing the code, or reading every line of agent reasoning. So I wrote a claude code hook that takes your session transcript and before creating a PR, extracts decisionsl, assumptions and trade-offs that were made during the session (and possibly missed by the human) and appends them to end of PR description. In my testing with another repo, it produced real insights that raised real risks, that would be otherwise lost. For now, it's only claude code, but I will add support for all other harnesses. I would appreciate if you try it out and it's open to contributions. |