Hacker News Reader

Some 5-line changes deserve a phd.

But yeah, most probably don’t.

Use your existing desired style as exemplars

My team solved this by creating a PR draft skill that clamps the length of the description to 3-5 sentences max. Those 3-5 sentences must only say WHAT is changing and WHY.

I find it to be far more useful than when humans wrote PR descriptions. Many engineers didn't write one, and those that did were poorly written... this problem is mostly solved for us.. it still has LLMism speak.. but it's useful enough for me to get the context I need to do my review.

The challenge of hard rules like this is that they're always overly restrictive. I've made multi-thousand file PRs that needed two lines of description including the title, and 5 line PRs that needed a 1hr presentation to fully explain them.

My personal guideline is that writing for humans should be done by humans.

I mean.. human judgment still applies. But as an automated first pass the clamp works in 90% of cases. I scan for correctness and make small edits here and there.

Your team can't spend effort to write 3-5 sentences by yourself ?

well... _of course_ the skill does more than write 3-5 sentences. We have a lot more that it automates into the description that makes it worth using.