comment-writer

Write warm, direct collaboration comments for PRs, issues, reviews, and Slack messages.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AD-Paladins/beaconator-web --skill comment-writer-ad-paladins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comment-writer
Source: https://github.com/AD-Paladins/beaconator-web/tree/main/.config/opencode/skills/comment-writer
Command: npx skills add https://github.com/AD-Paladins/beaconator-web --skill comment-writer-ad-paladins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing review feedback and collaboration comments that are both useful and well-received is hard: comments often come across as cold, overly long, or vague. This Skill provides a consistent voice and structure so every comment you write is actionable, warm, and concise. ## Core Features & Use Cases - Voice Rules: Enforces a warm, direct tone with concrete constraints like starting with the actionable point, keeping comments to 1-3 short paragraphs, and avoiding em dashes. - Comment Formula: Applies a repeatable structure of direct observation, reasoning, and concrete next action for every comment. - Language Matching: Automatically writes in the language of the target context, using neutral professional Spanish for Spanish threads unless told otherwise. - Use Case: Before leaving review feedback on a GitHub PR, load this Skill to produce a focused comment that addresses the highest-value issue with a clear technical reason and next step, instead of a scattered list of nitpicks. ## Quick Start Ask the assistant to write a review comment for a pull request using the comment-writer skill, for example by saying: write feedback asking the author to split this PR because it exceeds the 400-line budget.

Frequently Asked Questions about comment-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write better GitHub PR review comments?▼

Start with the actionable point instead of recapping the PR, explain the technical reason behind any requested change, and end with a concrete next action. Keep the comment to one to three short paragraphs or a tight bullet list.

What tone should code review feedback use?▼

Review feedback should be warm and direct, sounding like a thoughtful teammate rather than a corporate bot. Focus on the highest-value issue instead of listing every minor preference, and always explain why a change matters.

Can I write review comments in Spanish or other languages?▼

Yes, comments should match the language of the target context by default: Spanish threads get Spanish replies, English threads get English replies. For Spanish, use neutral professional Spanish unless the context calls for a regional tone.

How do I ask someone to split a large pull request?▼

State the concrete reason, such as exceeding a 400-line budget, then suggest a split order like foundation plus tests first, then integration, then docs. This gives each review a clear start and end.

When should I not comment on every issue in a PR?▼

Avoid pile-ons by commenting only on the highest-value issue rather than every small preference. This keeps reviews focused and prevents overwhelming the author with low-impact nitpicks.