skills.rest
verivend
verivendOFFICIAL
Explore all skills by this author →
Website𝕏@verivendGitHub

commit-conventions

Generate standardized commit messages following the Conventional Commits specification.

Updated Mar 10, 2026
Search Tags:#git#developer tools#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/verivend/verivend-vue3-template --skill commit-conventions-verivend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-conventions
Source: https://github.com/verivend/verivend-vue3-template/tree/main/.claude/skills/commit-conventions
Command: npx skills add https://github.com/verivend/verivend-vue3-template --skill commit-conventions-verivend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers create clear, consistent, and informative commit messages by adhering to the Conventional Commits specification, improving code history readability and automation.

Core Features & Use Cases

  • Enforces Conventional Commits: Guides users to format commit messages with type, scope, subject, and body.
  • Provides Type and Scope Guidance: Offers predefined lists of common commit types (feat, fix, chore, etc.) and scopes (grid, form, api, etc.).
  • Use Case: When committing a new feature that modifies the authentication flow, use this Skill to generate a feat(auth): add new login endpoint message, ensuring consistency across the team.

Quick Start

Generate a commit message for a bug fix in the grid component.

Frequently Asked Questions about commit-conventions

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

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

Conventional commit messages standardize git history by formatting commits with a type, optional scope, subject, and body. This structure ensures clarity for project scopes like UI, API, and configuration changes.

What does the conventional commits specification include in a commit message?▼

The conventional commits specification includes a commit type (such as feat or fix), an optional scope, a concise subject, and an optional body. This formatting enforces specific rules for code history readability and automation.

How do I format a feature commit for a specific code scope?▼

To format a feature commit, use the feat type followed by a scope in parentheses, such as feat(auth): add new login endpoint. This ensures consistency across team modifications to specific project areas like authentication.

What are the common types and scopes used in conventional commits?▼

Common conventional commit types include feat, fix, and chore, while predefined scopes often cover specific project areas like grid, form, and api. These options guide users in categorizing code changes accurately.

Can I use conventional commits for configuration changes and bug fixes?▼

Yes, conventional commits apply to all code commits across various project scopes, including configuration changes and bug fixes. You can generate messages like fix(grid): resolve rendering error to maintain consistent version control.

Related Skills

Explore More Software Engineering Skills→
forgivesam168forgivesam168
2

git-commit

Analyze diffs and stage changes to generate conventional git commit messages.

Community
Basic
manastalukdarmanastalukdar
1

changelog-auto

Generate changelogs from git commit history using conventional commit standards.

Community
Advanced
hairihouhairihou

git-conventions

Enforce Conventional Commits syntax for Git commit messages and branch naming.

Community
Basic
leodyversemilla07leodyversemilla07

git-workflow

Enforce conventional commit messages and branch naming conventions in Git workflows.

Community
Basic