commits

Standardize Git commit messages using the Conventional Commits format.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/pqem/agent-automatizado --skill commits-pqem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commits
Source: https://github.com/pqem/agent-automatizado/tree/main/templates/skills/generic/commits
Command: npx skills add https://github.com/pqem/agent-automatizado --skill commits-pqem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Conventional Commits format standardizes commit messages to improve changelog generation, review clarity, and automation across projects.

Core Features & Use Cases

  • Enforces a consistent type, scope, and description in commit messages.
  • Includes examples and clear rules for formatting, improving readability and tooling compatibility.
  • Use Case: when preparing releases or generating changelogs, standardized commits simplify changes tracking.

Quick Start

Create a conventional commit message using the template type(scope): description.

Frequently Asked Questions about commits

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

FAQPage Schema
What is a conventional commit message in Git?

You format conventional commits using the type(scope): description template. This enforces a consistent structure for categorizing changes, which enhances readability, simplifies changelog generation, and supports automation in Git workflows.

How do I standardize commit messages for changelog generation?

Use the conventional commits format with the type(scope): description pattern to standardize commit messages. This approach enforces consistent structure and categorization, directly simplifying changes tracking and release preparation.

When do I need to use the conventional commits format?

Use the conventional commits format when preparing releases or generating changelogs in Git workflows. It standardizes commit messages into a type(scope): description pattern, improving traceability and tooling compatibility for feature work and bug fixes.

Does the conventional commits format work for bug fixes and documentation updates?

Yes, conventional commits work for feature work, bug fixes, and documentation updates. The format enforces a consistent type, scope, and description pattern across all Git changes, improving traceability and tooling compatibility.

What are the rules for formatting a conventional commit scope?

Conventional commit scope formatting follows the type(scope): description pattern, placing the scope in parentheses after the type. The format provides specific rules and scope recommendations to ensure readability and tooling compatibility.