skills.rest
devbyray
devbyrayCOMMUNITY
Explore all skills by this author →
Website𝕏@devbyrayrayGitHub

commit-conventions

Validate Git commit messages against the Conventional Commits specification.

Updated Mar 13, 2026
Search Tags:#git#workflow#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/devbyray/nuxt-layers-component-lib-poc --skill commit-conventions-devbyray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-conventions
Source: https://github.com/devbyray/nuxt-layers-component-lib-poc/tree/main/.github/skills/commit-conventions
Command: npx skills add https://github.com/devbyray/nuxt-layers-component-lib-poc --skill commit-conventions-devbyray

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces a consistent and understandable format for Git commit messages, improving code history clarity and automation potential.

Core Features & Use Cases

  • Conventional Commits: Adheres to the widely adopted Conventional Commits specification for commit message structure.
  • Type and Scope: Encourages clear categorization of changes (feat, fix, docs, etc.) and their affected code areas.
  • Use Case: When making a bug fix, you'll use fix(auth): resolve login redirect issue to clearly communicate the change's nature and impact.

Quick Start

Use the commit-conventions skill to validate your git commit message.

Frequently Asked Questions about commit-conventions

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, run a shell script that checks your message structure for standardized types, scopes, and descriptions. This enforces a consistent format for improved code history clarity and automation.

What commit types are supported by the Conventional Commits specification?▼

The Conventional Commits specification supports types including feat, fix, docs, style, refactor, test, chore, perf, ci, and build. These types help categorize changes clearly within your version control history.

How do I format a bug fix message with a scope in git?▼

To format a bug fix message with a scope in git, use the structure `fix(scope): description`. For example, `fix(auth): resolve login redirect issue` clearly communicates the change's nature and affected code area.

Can I use optional scopes with conventional commit types?▼

Yes, you can use optional scopes with conventional commit types. The validation script enforces standardized commit types and descriptions while allowing optional scopes to specify the affected code areas.

Why enforce a standardized format for git commit messages?▼

Enforcing a standardized format for git commit messages improves code history clarity and enables automated changelog generation. Consistent types and scopes make it easier to track changes across version control.

Does this conventional commits validation require any dependencies?▼

No, this conventional commits validation requires no dependencies. It operates as a standalone shell script to validate your git commit messages against the specification.

Related Skills

Explore More Software Engineering Skills→
PiklarPiklar

speckit-git-initialize

Initialize a Git repository with an initial commit in Bash or PowerShell.

Community
Intermediate
allanninalallanninal
1

changelog-generator

Convert git commits into changelogs following Keep a Changelog and Conventional Commits.

Community
Intermediate
zhangzhang-111-izhangzhang-111-i
2

changelog-generator

Generate changelog entries from Conventional Commits in markdown or JSON.

Community
Intermediate
flowelflowel

setup-pre-commit

Automate Git pre-commit hook setup with Husky, lint-staged, and linters.

Community
Intermediate