conventional-comments

Format code-review feedback with labeled Conventional Comments.

7|Updated Feb 2, 2026

Search Tags:#formatting #code-review #labels #conventional-comments #decorations #actionable-feedback #review-best-practices

Ready to run

npx skills add https://github.com/milistu/agent-skills --skill conventional-comments-milistu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-comments
Source: https://github.com/milistu/agent-skills/tree/main/skills/conventional-comments
Command: npx skills add https://github.com/milistu/agent-skills --skill conventional-comments-milistu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comments in code reviews can be inconsistent and hard to act on. This Skill defines a structured format using Conventional Comments to ensure clarity, consistency, and actionable feedback across reviews.

Core Features & Use Cases

Enforces a single-word label for each comment to signify the issue type (praise, nitpick, suggestion, issue, todo, question, thought, chore, note).
Supports optional decorations like (non-blocking), (blocking), and custom tags to convey urgency and context.
Facilitates consistent PR feedback, RFC reviews, and peer reviews with easily greppable and grep-friendly messages.

Quick Start

Provide a review comment using the label issue and optional decoration (non-blocking) describing a problem and a proposed fix.

Frequently Asked Questions about conventional-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I format code review comments for actionable feedback?▼

Code review comments are formatted using the Conventional Comments standard, applying a single-word label like praise, nitpick, or issue to signify the type of feedback. This enforces clarity and consistency across peer reviews.

What are Conventional Comments and how do they structure PR reviews?▼

Conventional Comments structure PR reviews by prefixing feedback with a specific label such as todo, question, or thought. This standard makes review messages easily greppable and ensures actionable feedback across software teams.

How do I use decorations like non-blocking in code review feedback?▼

Decorations like (non-blocking) or (blocking) are added as optional tags to a labeled comment to convey urgency and context. They help developers quickly understand the severity of suggestions during peer reviews.

Can I use this structured comment format for RFC reviews and peer feedback?▼

Yes, the Conventional Comments standard applies to RFC reviews and peer feedback workflows across software teams. It enforces labeled, decorated, and actionable comments with clear rationale in any collaborative review context.

What is the best way to standardize code review messages across a team?▼

The best way to standardize code review messages is enforcing the Conventional Comments format, which requires a single-word label and optional decorations. This creates consistent, grep-friendly feedback across all pull requests.