contribution-voice

Keep it to one paragraph stating what changed and why, plus one sentence of validation. Avoid headings, bullet lists, and bold labels, since structure on a small point is the clearest sign of generated text.

A comment, reply, or bug report should be one to three sentences. State the cause and the fix directly, and cut anything that answers a question nobody asked.

Headings and bullets around a short point, repeated restatements of the same idea, emoji used as section markers, and identical structure across consecutive messages are the main tells. Plain prose at an appropriate length avoids them.

They are acceptable only when a template fixes the layout, such as a task or issue body with predefined sections. In that case the template owns the structure and the prose inside each section still follows the length and cut rules.

The cut pass removes duplicate examples of the same defect, statements that something works or is unaffected, and asides nobody asked about. After cutting, the draft is counted against its length budget, and being over budget means the pass is not finished.