skills.rest
intartif
intartifCOMMUNITY
Explore all skills by this author →
GitHub

conventional-commits

Format commit messages per Conventional Commits and validate with commitlint.

1|Updated Feb 12, 2026
Search Tags:#automation#git#commitlint#tooling#lint#commit-message#conventional-commits
One-click install
npx skills add https://github.com/intartif/demos-agent-skills --skill conventional-commits-intartif
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/intartif/demos-agent-skills/tree/main/.github/skills/conventional-commits
Command: npx skills add https://github.com/intartif/demos-agent-skills --skill conventional-commits-intartif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers generate commit messages that conform to the Conventional Commits standard and ensures they pass commitlint validation.

Core Features & Use Cases

  • Generate standard-conforming commit messages across types and optional scopes.
  • Validate messages against commitlint rules and provide guidance for updating subject length.
  • Use in Git workflows to review and enforce a consistent commit history across PRs.

Quick Start

Create a Conventional Commits message with type, optional scope, and a concise subject.

Frequently Asked Questions about conventional-commits

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

FAQPage Schema
How do I format git commit messages to pass commitlint validation?▼

To format git commit messages to pass commitlint, structure them using the Conventional Commits standard with an allowed type, optional kebab-case scope, and a concise subject to maintain a consistent history.

What is the Conventional Commits standard for git commit messages?▼

The Conventional Commits standard for git messages requires specifying a type, an optional scope, and a subject length limit to create uniform commit histories across development workflows.

How do I validate a range of git commits against commitlint rules?▼

You can validate a range of git commits against commitlint rules by generating a ready-to-use command that checks the commit history and provides guidance for updating subject length if validation fails.

Do I need to install dependencies to write conventional commits?▼

No dependencies are required to write conventional commits, as the formatting guidance for types and scopes is applied directly during your daily development workflow when preparing commits.

Why does commitlint reject my commit message subject?▼

Commitlint rejects your commit message subject when it exceeds the enforced length limit or lacks the required conventional type and optional kebab-case scope structure.

Related Skills

Explore More Software Engineering Skills→
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
rshadershade
3

commitlint

Validate commit messages against the Conventional Commits specification.

Community
Intermediate
ricardorochericardoroche
2

git-workflow-standards

Enforce conventional commits, branch naming, PR templates, and semantic versioning.

Community
Intermediate
kevinrobaynakevinrobayna

commit

Generate conventional Git commit messages from analyzed code changes.

Community
Intermediate