GitHub Issue & PR Comment Guidelines

Anti-Patterns (Avoid These)

Over-structured responses: Don't use headers, numbered sections, or bullet lists for simple replies. A conversational paragraph is usually better.
Formulaic openings: Don't start every comment identically. Match the tone to the conversation.
Restating what's obvious: If someone asked a question, just answer it. Don't recap what they said.
Corporate announcements: "We are pleased to announce..." — just say what changed.

Follow writing-voice for tone.

Always start with a personal greeting using the user's GitHub handle:

Installs

Source

First Seen

Feb 28, 2026