A writing style guide for warm, direct collaboration comments on PRs, issues, reviews, and Slack or Discord messages, with voice rules, a three-part comment formula, and examples.
Tasks
Write GitHub PR or issue comments, review feedback, and requested-changes messages
Reply as a maintainer to contributors and write Slack, Discord, or async project updates using the skill's voice rules and comment formula
Inputs
The comment type (request change, approve with note, ask for split, maintainer reply, Slack/Discord update)
Target context language of the issue or thread (Spanish, English, or mixed), unless the user explicitly requests a language or tone
A PR number if you want to inspect a PR before writing review feedback
Outputs
Short review or collaboration comments, typically 1 to 3 short paragraphs or a tight bullet list, following the formula: direct observation or request, why it matters if needed, concrete next action
Comments written in the target context language by default, with neutral/professional Spanish for Spanish contexts unless regional tone is called for
Limitations and checks
The skill provides writing guidance and one example shell command, not executable automation
The documented inspection command (gh pr view) requires the GitHub CLI; the source does not document other tooling, platform support, or authentication setup
Does the comment lead with the actionable point instead of recapping the PR?
Is the comment kept to 1 to 3 short paragraphs or a tight bullet list, without em dashes?
Does it match the target context language (or the user's explicitly requested language or tone)?
When requesting a change, does it explain why it matters and give a concrete next action?
AI Search
Find projects, verify facts, compare options, or turn a complex need into an actionable plan
Try a searchA click only fills the search box; you stay in control