From hax-yax
Formats code review and PR feedback using the Conventional Comments standard (label [decorations]: subject). Apply proactively whenever posting review comments or any critique of code or pull requests. Invoke directly when the user asks to format feedback, use conventional comments style, or label a review comment as blocking, suggestion, or nitpick.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hax-yax:format-review-commentsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Formats review comments using the [Conventional Comments](https://conventionalcomments.org/) standard, making intent unambiguous — readers know immediately whether a comment is blocking, optional, or informational.
Formats review comments using the Conventional Comments standard, making intent unambiguous — readers know immediately whether a comment is blocking, optional, or informational.
Apply this format proactively whenever you:
Use this format whenever you are reviewing anything — no explicit request needed.
When invoked directly to format existing comments:
references/conventional-comments-spec.md to confirm label and decoration meanings.label [decorations]: subject followed by an optional body on a new line.label [decorations]: subject
[body]
[discussion reference]
[blocking, if-minor])Read references/conventional-comments-spec.md before selecting labels for any comment that is not obviously a nitpick or praise.
| Label | Intent |
|---|---|
praise | Highlights something positive; never blocking |
nitpick | Minor style/preference issue; non-blocking by default |
suggestion | Proposes an improvement; non-blocking by default |
issue | Points out a problem that must be addressed; blocking by default |
todo | Small, unambiguous task the author should complete |
question | Asks for clarification; non-blocking |
thought | Shares an idea that doesn't warrant action |
chore | Simple housekeeping (rename, move, reformat); non-blocking |
note | Informational; no action required |
When selecting a label for an existing comment, match the comment's intent to the label definitions in references/conventional-comments-spec.md. When intent is ambiguous, prefer suggestion over issue and note over thought.
praise: clean abstraction here — easy to follow
suggestion: consider extracting this into a helper so it can be reused
issue [blocking]: this will panic on nil input; add a nil check before dereferencing
question: why is this sorted descending? just want to make sure it's intentional
nitpick: s/recieve/receive/
Example with body:
suggestion: extract the retry logic into a helper
This block appears in three places. A shared helper would make it easier to adjust the backoff strategy in one place.
Direct invocation — before and after:
Input:
This will crash on empty lists. Also the variable name is confusing.
Output:
issue [blocking]: this will crash on empty lists — add a guard before iterating
nitpick: variable name is unclear — consider renaming to reflect its purpose
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub geemus/plugins --plugin hax-yax