conventional-comments

Standardize code review feedback with Conventional Comments labels.

8|1|Updated Mar 28, 2026

Search Tags:#code review #best practices #feedback #pull request #communication

Ready to run

npx skills add https://github.com/bostonaholic/team --skill conventional-comments-bostonaholic

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates ambiguity and friction in code reviews by providing a structured, code-directed syntax that separates objective findings from subjective preferences.

Core Features & Use Cases

Standardized Labeling: Uses consistent tags like issue, suggestion, and nitpick to signal the severity and intent of feedback.
Collaborative Tone: Provides templates to shift feedback from person-directed criticism to code-directed analysis, reducing defensive responses.
Use Case: When reviewing a pull request, use this Skill to ensure every comment includes a file reference and a clear rationale, making it easier for the author to understand exactly what needs to be addressed and why.

Quick Start

Use the conventional-comments skill to format your feedback on the current pull request using the issue, suggestion, and nitpick labels.

Frequently Asked Questions about conventional-comments

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

FAQPage Schema

How do I standardize code review feedback for better clarity?▼

Standardize code review feedback by applying the Conventional Comments specification, which uses specific labeling syntax to separate objective findings from subjective preferences and reduce friction.

What are conventional comments in pull requests?▼

Conventional comments in pull requests are a structured syntax using labels like issue, suggestion, and nitpick to signal the severity and intent of code review feedback.

How do I write code-directed phrasing for technical documentation reviews?▼

Write code-directed phrasing for technical documentation reviews by using standardized labels and templates that shift feedback from person-directed criticism to objective analysis of the code.

Can I use conventional comments for security audits?▼

Yes, you can use conventional comments for security audits because the structured labeling syntax ensures objective findings and actionable feedback during the review process.

What is the best way to reduce defensive responses during code reviews?▼

Reduce defensive responses during code reviews by using collaborative tone templates that provide code-directed analysis with clear rationale instead of person-directed criticism.

How do I format pull request comments to include a clear rationale?▼

Format pull request comments by applying conventional labeling syntax with tags like issue and suggestion, ensuring every comment includes a file reference and a clear rationale.