> If they don't give a good summary, I ask them to write one.

Exactly; if people can't be bothered to describe (and justify) their work, or if they outsource it to AI that creates something overly wordy and possibly wrong, why should I be bothered to review it?

Yeah I did this too as an engineer!

I think this is a valid part of the "crafting PR" skill that's under appreciated, and part of the goal of Haystack here is to make that part of PR craft effortless.

How much time does it take you to craft the PR compared to writing the code? Just curious if crafting the PR becomes significantly easier with practice.