commitlint

Validate commit messages against the Conventional Commits specification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Validates commit messages against the Conventional Commits specification to ensure consistent, audit-friendly git history and streamlined changelog generation.

Core Features & Use Cases

  • Auto-detects and installs @commitlint/cli and @commitlint/config-conventional if missing.
  • Detects project-specific config or falls back to a safe default.
  • Validates type, scope, subject, and header/body/footer formats; reports actionable fixes and examples.

Quick Start

Validate the most recent commit against the Conventional Commits spec using npx commitlint.

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 the Conventional Commits specification?

To enforce Conventional Commits validation, this Skill checks your commit message type, scope, subject, and body formats, reporting concrete fixes and examples whenever validation errors occur during git workflows.

What is the best way to enforce consistent conventional commits for release tagging and pull requests?

Enforcing consistent conventional commits for release tagging and pull requests requires a linter that validates message types and scopes, ensuring an audit-friendly git history and streamlined changelog generation.

Do I need to manually install commitlint cli and config-conventional before validating commits?

No manual installation is needed; the Skill auto-detects and installs the commitlint cli and config-conventional packages, detects project-specific configurations, or falls back to a safe default to start validation.

Can I use commitlint validation with Node.js and JavaScript projects?

Yes, commitlint validation works with Node.js and JavaScript projects, applying during pre-commit checks and pull request preparation across JavaScript, Node.js, and other projects using conventional commits.

Why does commitlint validation fail on my commit message and how do I fix it?

Commitlint validation fails when your message violates the Conventional Commits specification; the Skill reports the exact validation errors with concrete fixes and examples to correct the type, scope, or subject format.