SkillAgentSearch skills...

comment-writer

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

Install / Use

npx skills add Gentleman-Programming/gentle-ai --skill comment-writer

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Our assessment of comment-writer

comment-writer scores 86/100 on our quality scale, 271st of 394 Communication skills we index.

Its SKILL.md is 2.3 KB long, well organised into 9 sections with 5 code examples: moderately detailed.

With 9,190 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
20/30
Structure
20/20
Description
15/15
Adoption
17/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so comment-writer is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

comment-writer compared with similar skills

All 4 of these similar skills score higher than comment-writer; compare them before choosing.

SkillScoreStarsUpdatedFormat
comment-writer (this skill)by Gentleman-Programming869.2k3d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server
LocalAIby mudler10050.4ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md

Frequently asked questions

How do I install comment-writer?
Run npx skills add Gentleman-Programming/gentle-ai --skill comment-writer. The install tabs above show the steps for each supported agent.
Which AI agents does comment-writer work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is comment-writer safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is comment-writer still maintained?
The repository was last updated 3 days ago, so comment-writer is actively maintained.

name: comment-writer description: "Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments." license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"

When to Use

Load this skill whenever you write a comment that another human will read.

Use it for:

  • GitHub PR or issue comments.
  • Review feedback and requested changes.
  • Maintainer replies.
  • Slack, Discord, or async project updates.

Voice Rules

| Rule | Requirement | |------|-------------| | Be useful fast | Start with the actionable point. Do not recap the whole PR before feedback. | | Be warm and direct | Sound like a thoughtful teammate, not a corporate bot. | | Keep it short | Prefer 1 to 3 short paragraphs or a tight bullet list. | | Explain why | Give the technical reason when asking for a change. | | Avoid pile-ons | Comment on the highest-value issue, not every tiny preference. | | Match target context language | Write in the target context language by default: Spanish issue/thread -> Spanish comment, English issue/thread -> English comment, mixed context -> target message language. If the user explicitly requests a language or tone, follow that request. For Spanish comments, use neutral/professional Spanish by default unless the user or target context clearly calls for regional tone. | | No em dashes | Use commas, periods, or parentheses instead. |

Comment Formula

<Direct observation or request>

<Why it matters, only if needed>

<Concrete next action>

Examples

Request change

Good approach overall. I'd split this into a separate commit because it mixes validation logic with UI wiring.

That keeps the reviewer's focus narrower and makes rollback cleaner if the integration fails.

Approve with a note

Approved. The scope is clear and the change is well-contained.

For the next PR, add links to the previous and following PRs so the chain stays navigable.

Ask for split

This PR exceeds the 400-line budget, so we need to split it or justify `size:exception`.

Suggested order: foundation + tests first, then integration, then docs. That gives each review a clear start and end.

Commands

# Inspect a PR before writing review feedback
gh pr view <PR_NUMBER> --json title,body,additions,deletions,changedFiles

Related Skills

View on GitHub
GitHub Stars9.2k
CategoryCommunication
Updated3d ago
Forks898

Languages

Go

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
comment-writer — Universal Skill: Install & Safety Check | SkillAgent