Except, no it doesn’t.

In the case of a pull request, I am not about to trust some LLM that has no business context and can only pretend to guess at the “why” of a change.

To understand the “what” of a change, you have to actually read the code. This doesn’t belong in the pull request description most of the time.