skills.rest
knguyen0125
knguyen0125COMMUNITY
Explore all skills by this author →
GitHub

commit

Generate and validate conventional git commit messages with optional scope and override.

Updated Feb 11, 2026
Search Tags:#git#commit#commitlint#lint#conventional-commits#message#scopes
One-click install
npx skills add https://github.com/knguyen0125/claude-plugin --skill commit-knguyen0125
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/knguyen0125/claude-plugin/tree/main/plugins/engineering/skills/commit
Command: npx skills add https://github.com/knguyen0125/claude-plugin --skill commit-knguyen0125

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams create consistent, conventional git commit messages that follow established formatting rules, reducing confusion and improving changelog quality.

Core Features & Use Cases

  • Enforces Conventional Commits structure (type, optional scope, description) for every commit.
  • Accepts an optional OVERRIDE_MESSAGE to replace the generated message while validating format.
  • Provides a deterministic workflow for composing commits aligned with project conventions during code changes, reviews, and releases.

Quick Start

Generate a conventional commit message for the current changes using the defined rules.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commit messages for git?▼

Creating conventional commit messages for git requires structuring changes with a valid type, optional scope, and description. This skill streamlines that workflow by validating your commit structure against the Conventional Commits format to ensure consistent project history.

What is the Conventional Commits format for a git commit message?▼

The Conventional Commits format structures a git commit message with a specific type, an optional scope, and a descriptive summary. This ensures consistent history across teams and improves overall changelog quality during code reviews and releases.

Can I override the generated conventional commit message?▼

Yes, you can override the generated conventional commit message by supplying an OVERRIDE_MESSAGE. The skill accepts this input and validates it against the required type, optional scope, and description structure to maintain formatting compliance.

Does commitlint work with scopes in conventional commits?▼

Commitlint validates conventional commits by enforcing the commit type, optional scope, and description. This skill applies these commitlint rules to your code changes, PR preparations, and release workflows to guarantee deterministic messaging aligned with project conventions.

When do I need to use conventional commits in my release workflow?▼

You need conventional commits in your release workflow when you require consistent history and high-quality changelogs across team collaborations. Applying standardized messaging during code changes and PR preparations reduces confusion and automates release note generation.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

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

Community
Intermediate
ehtbantonehtbanton

commitlint-config-generator

Generate commitlint configuration files enforcing Conventional Commits 1.0.0 standards.

Community
Basic
74nu574nu5

git-commit

Generate conventional commit messages from diffs and stage files.

Community
Intermediate