comment-writer

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

Updated Jun 5, 2026

Search Tags:#code review #feedback #collaboration #pull request #github #communication #comment writing

Ready to run

npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill comment-writer-zmynxx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: comment-writer
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/comment-writer
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill comment-writer-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing review feedback and issue replies that are both useful and human is hard: comments often come out too long, too blunt, or too vague. This Skill gives you a consistent voice and structure for every comment a teammate will read. ## Core Features & Use Cases - Voice Rules: Enforces warm, direct, concise writing with actionable points first and technical reasoning for requested changes. - Comment Formula: Structures feedback as observation, rationale, and concrete next action. - Language Matching: Automatically writes in the language of the target thread (Spanish, English, or mixed contexts). - Use Case: Before leaving PR review feedback, inspect the change with `gh pr view <PR_NUMBER>` and produce a short, focused comment that requests a split or approves with a note. ## Quick Start Write a review comment for PR 42 asking the author to split the validation logic into a separate commit.

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 for any requested change, and keep it to one to three short paragraphs. Focus on the highest-value issue rather than listing every minor preference.

How to give code review feedback without sounding harsh?▼

Use a warm but direct tone: state the observation, briefly explain why it matters, and end with a concrete next action. Sound like a thoughtful teammate rather than a corporate bot, and avoid piling on minor nitpicks.

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

Yes, the comment matches the language of the target thread by default: Spanish issues get Spanish replies, English threads get English. For Spanish, it uses neutral professional Spanish unless the context calls for 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 scope and size. This lets you ground feedback in the actual change, such as requesting a split when the PR exceeds a line budget.

When should I ask for a PR to be split instead of approving?▼

Request a split when a PR exceeds the team's size budget or mixes unrelated concerns, such as validation logic with UI wiring. Suggest a concrete order, like foundation and tests first, then integration, then docs.