How does your team handle PR descriptions?

[Jeffrin-dev]

Curious how contributors here approach PR descriptions —
do you have a template, or is it freeform?

I ask because I'm building a GitHub App that auto-generates
PR descriptions from the diff. It reads what actually changed
and writes a structured description: what changed, why,
how to test, what to watch for.

Before I go further building it — does this solve a real
problem for you, or does your team already have a good system?

If you're curious: https://prdraft.carrd.co/
Happy to give early access to anyone who wants to try it.

[icyJoseph]

This is off-topic. Doesn't GitHub have a discussion forum for this kind of question?