conventional-comments

Format code review feedback with Conventional Comments labels and decorations.

6|3|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Jitsusama/agentic-harness.pi --skill conventional-comments-jitsusama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventional-comments
Source: https://github.com/Jitsusama/agentic-harness.pi/tree/main/skills/conventional-comments
Command: npx skills add https://github.com/Jitsusama/agentic-harness.pi --skill conventional-comments-jitsusama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all code review feedback is constructive, clear, and follows a standardized, professional format, improving communication and reducing misunderstandings.

Core Features & Use Cases

  • Structured Feedback: Organizes comments with clear labels, optional decorations, and detailed discussions.
  • Tone Guidance: Promotes a helpful, instructional, and polite tone in all feedback.
  • Use Case: When reviewing a colleague's code, use this Skill to format your suggestions, issues, or praise in a way that is easily understood and actionable.

Quick Start

Use the conventional-comments skill to format your feedback as a suggestion with a non-blocking decoration.

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 feedback to be more constructive and professional?

Formatting code review feedback professionally requires applying standardized labels, decorations, and tone guidance. This ensures comments are structured with clear labels and detailed discussions, making suggestions easily understood and actionable for colleagues.

What is the conventional comments format for structuring code review observations?

The conventional comments format structures code review observations using specific labels, optional decorations, and detailed discussions. It organizes feedback into categories like suggestions or issues, ensuring clarity and reducing misunderstandings during collaboration.

How do I write code review suggestions that are polite and instructional?

Writing polite and instructional code review suggestions involves enforcing Canadian-polite communication standards and instructional tone guidance. This approach promotes a helpful tone, ensuring feedback is formatted as a non-blocking suggestion with clear, actionable discussions.

Does this code review formatting approach work for both blocking and non-blocking feedback?

Yes, this code review formatting approach supports both blocking and non-blocking feedback through optional decorations. You can format feedback as a non-blocking suggestion or apply specific decorations to indicate the severity and actionability of the observation.

When do I need to use standardized labels for code review comments?

Standardized labels for code review comments are needed when you want to improve communication and reduce misunderstandings. Using labels ensures that feedback is constructive, clear, and easily understood by colleagues during collaboration.

Can I use this to format praise and positive observations during a code review?

Yes, you can use this to format praise and positive observations during a code review. The structured feedback format applies to all agent-generated review comments, allowing you to categorize praise with appropriate labels and detailed discussions.