concise-pr-comments

Lead with the verdict in the first sentence, keep comments to 1-3 sentences, and cover one idea per comment. Use first person plainly, cite evidence as file.ts:123 with inline backticks, and end with a direct question when the author should make the call.

Replies can be one word: "Done", "Fixed", or "Good to know, didn't know that. Resolved". Skip agreement openers like "Makes sense" and start at the part the author does not already know, then resolve the thread.

Common tells include inventory dumps of everything that changed, filler transitions like "just flagging it", three-part parallel constructions, headers or bullets inside inline comments, and self-summarizing phrases like "a clean, backwards-compatible API addition".

Yes, the same rules apply to Azure DevOps, GitHub, and Jira work-item and issue comments, plus PR descriptions. Any text posted where other people will read it follows the verdict-first, short-paragraph style.

A long comment is only justified when the evidence itself is the point, such as a traced code path, compiled output, or reproduced failure. Even then it stays as plain paragraphs without headers or bullet lists.