commitlint

Validate commit messages against the Conventional Commits specification in Node.js git environments.

19|3|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/dirien/yet-another-agent-harness --skill commitlint-dirien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commitlint
Source: https://github.com/dirien/yet-another-agent-harness/tree/main/.claude/skills/commitlint
Command: npx skills add https://github.com/dirien/yet-another-agent-harness --skill commitlint-dirien

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enforces a consistent commit message format so teams can generate changelogs, apply semantic versioning, and maintain a readable git history across repositories.

Core Features & Use Cases

  • Installation and Environment Checks: Detects whether @commitlint/cli and @commitlint/config-conventional are available and attempts to install them when missing, with clear remediation guidance if installation fails.
  • Config Detection and Fallbacks: Uses project-specific commitlint configuration when present and falls back to a sensible default configuration sourced from the included reference document.
  • Message Validation and Reporting: Validates commit messages (from strings, files, or the last git commit), reports each failing rule with an explanation and concrete fix suggestions, and supports iterative re-validation.
  • Use Case: Run as a pre-commit or CI check to block invalid messages, or use when preparing pull requests to ensure titles and messages follow team conventions.

Quick Start

Validate the most recent git commit message and receive precise failure reasons and suggested fixes for any Conventional Commits violations.

Frequently Asked Questions about commitlint

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

FAQPage Schema
How do I validate git commit messages against Conventional Commits?

To validate git commit messages against Conventional Commits, this Skill checks messages from strings, files, or the last git commit and reports failing rules with explanations and fix suggestions. It operates in Node.js environments.

What is Conventional Commits validation used for?

Conventional Commits validation enforces a consistent commit message format so teams can generate changelogs, apply semantic versioning, and maintain a readable git history across repositories. It is commonly used as a pre-commit hook or CI check.

Do I need to install commitlint manually before using this?

You do not need to install commitlint manually; the Skill auto-detects and installs @commitlint/cli and @commitlint/config-conventional when missing. It provides remediation guidance if installation fails.

Can I use this for pull request preparation and CI validation?

Yes, you can use this for pull request preparation and CI validation to block invalid messages and ensure titles follow team conventions. It applies to any git repository running in Node.js npx environments.

What happens if my project lacks a commitlint configuration file?

If your project lacks a commitlint configuration, the Skill falls back to a sensible default configuration sourced from an included reference document. It prioritizes project-specific commitlint configuration when present.