comment-writer

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/Alountk/Bloodbowl_Project --skill comment-writer-alountk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comment-writer
Source: https://github.com/Alountk/Bloodbowl_Project/tree/main/.opencode/skills/comment-writer
Command: npx skills add https://github.com/Alountk/Bloodbowl_Project --skill comment-writer-alountk

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 end up too long, too blunt, or buried in recap. 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 short paragraphs, actionable openings, and explanations of why a change matters. - Comment formula: Structures feedback as observation, reasoning, and concrete next action. - Language matching: Writes in the target thread's language (Spanish or English) by default, with neutral professional Spanish unless otherwise requested. - Use Case: Before leaving PR review feedback, inspect the PR with gh pr view <PR_NUMBER> and then draft a request-changes comment that leads with the key issue and a suggested split order. ## Quick Start Ask the assistant to write a review comment for a pull request that requests splitting an oversized PR into smaller commits.

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 pull request review comments?▼

Lead with the actionable point instead of recapping the PR, explain the technical reason behind each requested change, and keep it to one to three short paragraphs. Focus on the highest-value issue rather than listing every minor preference.

What is a good structure for code review feedback?▼

Use a three-part formula: a direct observation or request, a brief explanation of why it matters, and a concrete next action. This keeps feedback clear, respectful, and easy for the author to act on.

Can I write GitHub comments in Spanish with this skill?▼

Yes, the skill matches the target thread's language by default, so a Spanish issue gets a Spanish comment. It uses neutral professional Spanish unless the context or user explicitly requests a regional tone.

How do I inspect a PR before writing review feedback?▼

Run gh pr view <PR_NUMBER> --json title,body,additions,deletions,changedFiles to see the PR's scope and changed files. This gives you the context needed to write specific, grounded feedback.

When should I avoid commenting on every issue in a review?▼

Avoid pile-ons by commenting only on the highest-value issue rather than every small preference. This keeps reviews focused and prevents authors from feeling overwhelmed by nitpicks.