comment-writer

Write concise GitHub PR review comments with action-first structure.

2|Updated Jul 29, 2025

Search Tags:#code review #github #async communication #actionable feedback #comment writing #issue replies #collaboration tone

Ready to run

npx skills add https://github.com/kurojs/EnderDots --skill comment-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: comment-writer
Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/comment-writer
Command: npx skills add https://github.com/kurojs/EnderDots --skill comment-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you communicate actionable review feedback clearly and respectfully, so collaborators can understand what to change quickly and move forward without friction.

Core Features & Use Cases

Warm, direct collaboration tone: Produces teammate-like feedback that feels considerate rather than robotic.
Action-first review structure: Starts with the most important point instead of rehashing the entire thread.
Practical change guidance: Includes the technical why when requesting changes and suggests concrete next actions.
Thread-aware writing: Matches the language or phrasing of the thread (including locale-specific variants).

Quick Start

Use comment-writer to draft a concise GitHub PR review comment that states the key feedback first, explains the technical reason, and ends with a clear next action.

Frequently Asked Questions about comment-writer

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

FAQPage Schema

How do I write actionable GitHub PR comments that don't sound robotic?▼

To write actionable GitHub PR comments, use an action-first structure that leads with the key feedback, includes a brief technical rationale, and ends with a clear next step. This approach ensures the review comment is warm, direct, and concise without piling on.

What is the best way to reply to GitHub issues with clear next actions?▼

The best way to reply to GitHub issues is to start with the most important point rather than rehashing the thread. Provide practical change guidance with a concise technical explanation and match the language or locale used in the original issue thread.

How do I keep async code review feedback concise and respectful?▼

To keep async code review feedback concise and respectful, avoid pile-ons and rehashing the thread. State the key feedback first, explain the technical reason for the change, and provide a clear, warm direction for the collaborator's next action.

Does this comment writing approach support matching different languages in a thread?▼

Yes, this comment writing approach supports thread-aware language matching. It automatically mirrors the language and locale-specific phrasing used in the existing GitHub PR or issue thread to maintain consistent async communication.

Can I use this for maintainer replies on complex PR threads?▼

Yes, you can use this for maintainer replies on complex PR threads. It translates lengthy code review feedback into brief, actionable guidance by prioritizing the primary issue first and avoiding unnecessary pile-ons across multiple comments.