Skip to content

Gentleman-Programming/gentle-ai / internal/assets/skills/comment-writer

comment-writer

Verified

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

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

RuleRequirement
Be useful fastStart with the actionable point. Do not recap the whole PR before feedback.
Be warm and directSound like a thoughtful teammate, not a corporate bot.
Keep it shortPrefer 1 to 3 short paragraphs or a tight bullet list.
Explain whyGive the technical reason when asking for a change.
Avoid pile-onsComment on the highest-value issue, not every tiny preference.
Match target context languageWrite 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 dashesUse 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 is large for one review (about 600 changed lines). Could we split it, or follow the repo's size policy if it allows one PR?

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
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall