I don't need an AI generated PR summary because the AI is unlikely to understand why the changes are being made, and specifically why you took the approach(es) that you did.
I can see the code, I know what changed. Give me the logic behind this change. Tell me what issues you ran into during the implementation and how you solved them. Tell me what other approaches you considered and ruled out.
Just saying "This change un-links frobulation from reticulating splines by doing the following" isn't useful. It's like adding code comments that tell you what the next line does; if I want to know that I'll just read the next line.
But I explained to the AI why we're doing the change. When the AI and I try something and we fail I explain that and it's included in the PR.
The AI has far more energy than I do when it comes to writing PR summaries, I have done it so many times, it's not the main part of my job. I have already provided all the information for a PR, why should I repeat myself? What happened to DRY?