<< All versions

Skill v1.0.0

currentAutomated scan100/100
josedowski/axioma/comment-writer
──Details
PublishedSeptember 27, 2026 at 10:01 PM
Content Hashsha256:cb980612f7237b31...
Git SHAac486344c3fc
──Files
Files (1 file, 2.4 KB)
SKILL.md2.4 KBactive
SKILL.md · 76 lines · 2.4 KB

version: "1.0.0" 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

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

text
<Direct observation or request>
<Why it matters, only if needed>
<Concrete next action>

Examples

Request change

markdown
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

markdown
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

markdown
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

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