skills.rest
jhannka
jhannkaCOMMUNITY
Explore all skills by this author →
GitHub

comment-writer

Write warm, direct comments for PR reviews, issues, and team messages.

Updated Aug 28, 2026
Search Tags:#code review#feedback#collaboration#pull request#github#communication#comment writing
One-click install
npx skills add https://github.com/jhannka/php-skills --skill comment-writer-jhannka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comment-writer
Source: https://github.com/jhannka/php-skills/tree/main/skills/comment-writer
Command: npx skills add https://github.com/jhannka/php-skills --skill comment-writer-jhannka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing review feedback and issue replies that are both kind and actionable is hard; comments often end up too blunt, too vague, or buried in unnecessary recap. This Skill provides voice rules and a repeatable structure so every comment a human reads is useful, warm, and short. ## Core Features & Use Cases - Voice Rules: Enforces actionable-first structure, warmth without corporate tone, brevity (1-3 short paragraphs), and technical justification for requested changes. - Comment Formula: A three-part template (observation, why it matters, concrete next action) for consistent feedback. - Language Matching: Automatically matches the target thread's language, with neutral professional Spanish as the default for Spanish contexts. - Use Case: Before replying to a GitHub PR that mixes validation logic with UI wiring, use this Skill to draft a concise change request that explains the reasoning and suggests splitting the commit. ## Quick Start Use the comment-writer skill to draft review feedback 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 pull request 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. Follow the formula: direct observation, why it matters, then a concrete next action.

How to give code review feedback without sounding harsh?▼

Sound like a thoughtful teammate by being warm and direct: state the observation plainly, justify it technically, and avoid pile-ons by commenting only on the highest-value issue rather than every minor preference.

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

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

What is the ideal length for a PR review comment?▼

Prefer one to three short paragraphs or a tight bullet list. Lead with the actionable point and include the reasoning only if needed, so reviewers and authors stay focused.

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

It is designed for human-readable collaboration comments like PR feedback, issue replies, and Slack updates. It does not apply to commit messages, code documentation, or automated bot messages.

Related Skills

Explore More Content & Communication Skills→
gittowergittower
413

pr-review

Create a structured GitHub pull request review draft with inline comments.

Official
Advanced
jp5labsjp5labs
1

forge-respond

Triages unresolved GitHub PR review threads and executes approved fixes, deferrals, and replies.

Official
Advanced
tta-labtta-lab
23

triage

Assesses PR review comments and posts structured re-review updates to Git-based pull requests.

Official
Intermediate
streamlitstreamlit
45.7k

addressing-pr-review-comments

Fetches, categorizes, and resolves GitHub PR review comments using the gh CLI.

Official
Intermediate