conventional-comments

Format review feedback into Conventional Comments for Azure DevOps pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jamesbondev/ai-dotfiles --skill conventional-comments-jamesbondev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventional-comments
Source: https://github.com/jamesbondev/ai-dotfiles/tree/main/.github/skills/conventional-comments
Command: npx skills add https://github.com/jamesbondev/ai-dotfiles --skill conventional-comments-jamesbondev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes code review feedback by formatting it according to the Conventional Comments standard, making it clearer, more actionable, and easier to process for both developers and automated systems.

Core Features & Use Cases

  • Structured Feedback: Organizes review comments with clear labels, optional decorations, and concise subjects.
  • Severity Mapping: Maps general code review severity to specific Conventional Comment labels and decorations.
  • Use Case: When reviewing a pull request, use this Skill to ensure all feedback, from minor style suggestions to critical bugs, is formatted consistently for Azure DevOps PRs.

Quick Start

Format the following review comment as a conventional comment: "The security check for user input is missing, which could lead to injection vulnerabilities. Please add input sanitization."

Frequently Asked Questions about conventional-comments

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

FAQPage Schema
How do I format pull request feedback as conventional comments in Azure DevOps?

To format pull request feedback as conventional comments, apply a defined label and decoration schema to your review text. This maps severity to structured labels for clear, actionable Azure DevOps PR comments.

What are conventional comments and why use them for code review?

Conventional comments standardize code review feedback by organizing text with clear labels, optional decorations, and concise subjects. This makes feedback clearer and easier to process for developers and automated systems.

How do I map code review severity to conventional comment labels?

Mapping code review severity to conventional comment labels involves applying a defined schema that decorates feedback with domain-specific concerns. This translates general severity into specific structured labels.

Can I use conventional comments for automated pull request processing?

Yes, conventional comments are designed for automated pull request processing. By formatting feedback with a strict label and decoration schema, automated systems can easily parse and act on the structured comments.

Do I need any specific tools to generate structured PR comments?

No specific external tools are required to generate structured PR comments. You can format your review text into conventional comments by adhering to the defined label and decoration schema directly.

What limitations exist when formatting Azure DevOps PR feedback?

A limitation of formatting Azure DevOps PR feedback is that it strictly requires adherence to a defined label and decoration schema. Feedback outside this conventional comments structure may not parse correctly.