comment-writer

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

Updated May 24, 2026
One-click install
npx skills add https://github.com/etrigan16/v0-cipher-ar --skill comment-writer-etrigan16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comment-writer
Source: https://github.com/etrigan16/v0-cipher-ar/tree/main/.opencode/skills/comment-writer
Command: npx skills add https://github.com/etrigan16/v0-cipher-ar --skill comment-writer-etrigan16

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing review feedback and issue replies that are both useful and respectful is hard; comments often end up too long, too vague, or unintentionally harsh. This Skill provides a clear voice framework so every comment you write is actionable, warm, and concise. ## Core Features & Use Cases - Voice Rules: Enforces actionable-first structure, warmth with directness, brevity, and technical justification for requested changes. - Comment Formula: A repeatable pattern of observation, reasoning, and concrete next action for consistent feedback. - Language Matching: Automatically writes in the language of the target thread, with neutral professional Spanish or English by default. - Use Case: When reviewing a teammate's oversized pull request, use this Skill to write a short comment that asks for a split, explains why, and suggests a concrete ordering of the smaller PRs. ## Quick Start Ask the assistant to write review feedback for a pull request using the comment-writer guidelines, for example: "Write a PR comment asking the author to split this change 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?▼

Start with the actionable point instead of recapping the PR, keep it to one to three short paragraphs, and explain the technical reason behind any requested change. End with a concrete next action so the author knows exactly what to do.

How to give code review feedback without sounding harsh?▼

Be warm and direct like a thoughtful teammate, not a corporate bot. Focus on the highest-value issue rather than piling on every small preference, and always explain why a change matters.

Does this Skill support writing comments in Spanish?▼

Yes, it matches the language of the target context by default, so a Spanish issue or thread gets a Spanish comment. It uses neutral professional Spanish unless the user or context calls for a regional tone.

What is the recommended structure for a review comment?▼

Use the three-part formula: a direct observation or request, an explanation of why it matters only if needed, and a concrete next action. This keeps feedback short and immediately actionable.

When should I not use this comment-writing approach?▼

It is designed for human-readable collaboration comments like PRs, issues, and chat updates. It is not intended for automated commit messages, documentation, or formal release notes.