AI Comment Writer

Installation

1. 1
   Make sure Claude is on your device and in your terminal.

   Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

   One-time setup

   Copy

   npm i -g @anthropic-ai/claude-code

   Already have it? Skip ahead.

2. 2
   Paste into Claude Code or into your terminal.

   Install

   Sign up to copy

   git clone ht••••••••••••••••••••••••••••••••••••••••••••••••••••••• •••••••••••••••••••••••••••••••••••••••• •• ••••• •• ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• •• •• •• •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

   Sign up free to reveal

   This copies the whole skill folder into ~/.claude/skills/gentle-ai-comment-writer-gentleman-programming/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

   Faster alternative (instruction-only skills)

   Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

   Quick install (SKILL.md only)

   Sign up to copy

   mkdir -p ~/.•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• •• •••• ••••• •••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• •• ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

   Sign up free to reveal
3. 3
   Restart Claude Code.

   Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

4. 4
   Just ask Claude.

   Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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

What this skill does

<Direct observation or request>

<Why it matters, only if needed>

<Concrete next action>

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.

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.

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.

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