skills.rest
kevinslin
kevinslinCOMMUNITY
Explore all skills by this author →
Website𝕏@kevins8GitHub

dev.conventional-commits

Explain and apply the Conventional Commits specification for commit messages.

21|Updated Jan 3, 2026
Search Tags:#git#linting#versioning#best-practices#code-review#conventional-commits#commit-messages
One-click install
npx skills add https://github.com/kevinslin/skills --skill dev-conventional-commits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev.conventional-commits
Source: https://github.com/kevinslin/skills/tree/main/active/dev.conventional-commits
Command: npx skills add https://github.com/kevinslin/skills --skill dev-conventional-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting and validating commit messages to enforce a standardized, readable project history and smoother release processes.

Core Features & Use Cases

  • Define and enforce commit types, scopes, and breaking-change notation.
  • Provide examples for drafting, validating, and reviewing commits.
  • Support onboarding and tooling integration with Git workflows and release pipelines.

Quick Start

Draft a Conventional Commits message for adding a new feature to the authentication module.

Frequently Asked Questions about dev.conventional-commits

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

FAQPage Schema
What is a conventional commit message and when do I need it?▼

Conventional commits use a standardized format with required types, scopes, and breaking-change notation to enforce a readable project history. You need it for smoother release processes and clearer code review communication.

How do I format a conventional commit for a new feature with a breaking change?▼

Format conventional commits by specifying the type, optional scope, and breaking-change notation. For a new authentication feature, use `feat(auth): description` and add `BREAKING CHANGE:` details in the commit body.

How do I validate git commit messages during code review?▼

Validate git commit messages by checking required format, verifying correct naming, scope, and breaking-change handling against the Conventional Commits specification during code review.

Does conventional commits work with existing Git workflows and release pipelines?▼

Conventional commits integrate with existing Git workflows and release pipelines to support onboarding and tooling integration, ensuring standardized commit messages that smooth release processes and maintain readable project history.

What are the limitations of using conventional commits for code review?▼

Conventional commits require strict adherence to the specification for types, scopes, and breaking-change notation. Limitations include the learning curve for drafting valid messages and the need for consistent enforcement across all contributors during code review.

Related Skills

Explore More Software Engineering Skills→
0xrafasec0xrafasec
9

commit

Stage and commit git changes with conventional commit messages.

Community
Intermediate
proofgeistproofgeist
17

create-changeset

Generate version bump changesets from git commit history for monorepo packages.

Official
Advanced
JNZader-VaultJNZader-Vault

ci-local-guide

Run CI/CD pipelines locally in Docker with automated detection, linting, and testing.

Official
Intermediate
mcj-codermcj-coder
1

branching-strategy-and-conventions

Configure Git branching strategies, Conventional Commits, and merge rules.

Community
Advanced