skills.rest
oscardlfr
oscardlfrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-lint

Validates and rewrites commit messages using Conventional Commits v1.0.0 grammar.

1|Updated Mar 9, 2026
Search Tags:#git#commit#conventional commits#validation#lint
One-click install
npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill commit-lint-oscardlfr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-lint
Source: https://github.com/oscardlfr/AndroidCommonDoc/tree/main/skills/commit-lint
Command: npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill commit-lint-oscardlfr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Grep, Glob, Edit, and includes scripts (resource) components.

What problem does it solve?

This Skill helps maintain a consistent commit message format, adhering to the Conventional Commits standard, which is crucial for project maintainability and readability.

Core Features & Use Cases

  • Validation: Checks commit messages against the Conventional Commits v1.0.0 grammar.
  • Fixing: Interactively rewrites non-conforming commit messages.
  • Scope and Type Validation: Ensures that commit scopes and types are defined according to project standards.
  • Use Case: When you want to enforce a standard commit message format across your team to improve commit history readability and maintainability.

Quick Start

Run the commit-lint skill to validate the current commit message.

Frequently Asked Questions about commit-lint

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

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

You can validate git commit messages by running the skill to check them against the Conventional Commits v1.0.0 grammar. It analyzes your commit history to ensure consistent formatting, improving project maintainability and readability.

What is the best way to enforce conventional commit formatting across a software development team?▼

The best way to enforce conventional commit formatting is using a validation skill that checks scopes and types against project standards. It ensures team-wide commit history consistency by validating messages against the v1.0.0 specification.

Can I automatically fix non-conforming git commit messages?▼

Yes, you can automatically fix non-conforming git commit messages. The skill interactively rewrites messages that fail validation, ensuring they adhere to the defined Conventional Commits grammar and project scope standards.

Does this commit validation tool work within any software development project environment?▼

Yes, this commit validation tool operates within the scope of any software development project. It requires Bash, Read, Grep, Glob, and Edit commands to perform message validation and rewriting against conventional standards.

When do I need to use Conventional Commits validation for my git history?▼

You need Conventional Commits validation when you want to enforce a standard commit message format across your team. This practice is crucial for improving commit history readability and long-term project maintainability.

Related Skills

Explore More Software Engineering Skills→
Destynova2Destynova2
5

cli-git-conventional

Enforce Conventional Commits v1.0.0 and remove AI markers from git commits.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
bailynlovebailynlove
1

requesting-code-review

Automate pre-commit code verification with static security scanning and quality gates.

Community
Advanced
diriendirien
19

commitlint

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

Community
Intermediate