Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/comment-writer
Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.
Passed 12 of 22 test cases with the skill, and 4 of 22 without it.
and 11 more in the full report
8 fixed4 passed either way10 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write a shell command using GitHub CLI to inspect pull request #452 before drafting review comments, retrieving its title, body, lines added, lines deleted, and list of changed files in JSON format.
| Checked | Without skill | With skill |
|---|---|---|
| The command calls `gh pr view 452`. | Passed | Passed |
| The command passes `--json title,body,additions,deletions,changedFiles`. | Missed | Passed |
The instructions your model reads when the skill loads.
Load this skill whenever you write a comment that another human will read.
Use it for:
| 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. |
<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.
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.