skills.rest
jamesbondev
jamesbondevCOMMUNITY
Explore all skills by this author →
GitHub

git-committing

Enforce Conventional Commits format for Git commit messages.

Updated Aug 23, 2026
Search Tags:#code quality#git#developer tools#version control#commit#conventional commits
One-click install
npx skills add https://github.com/jamesbondev/ai-dotfiles --skill git-committing-jamesbondev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-committing
Source: https://github.com/jamesbondev/ai-dotfiles/tree/main/.github/skills/git-committing
Command: npx skills add https://github.com/jamesbondev/ai-dotfiles --skill git-committing-jamesbondev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you adhere to the Conventional Commits specification, ensuring your Git commit messages are standardized, informative, and machine-readable.

Core Features & Use Cases

  • Standardized Commit Format: Enforces a consistent structure for commit messages (<type>(<scope>): <description>).
  • Type Selection Guidance: Provides clear definitions for commit types (feat, fix, refactor, etc.).
  • Scope Derivation: Offers strategies for determining the appropriate scope for your commits.
  • Description Best Practices: Outlines rules for writing concise and descriptive commit summaries.
  • Workflow Integration: Adapts commit type selection based on the development workflow (e.g., TDD, Bug-fix).

Quick Start

Use the git-committing skill to generate a conventional commit message for a new feature.

Frequently Asked Questions about git-committing

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

FAQPage Schema
What is the conventional commits format for git commit messages?▼

The conventional commits format structures git commit messages using the pattern `<type>(<scope>): <description>`. This specification ensures your commit history is standardized, informative, and machine-readable for software development projects.

How do I write a conventional commit message for a new feature?▼

To write a conventional commit message, select the appropriate type like `feat` for new features, derive the scope, and write a concise description. The git-committing skill guides this process to ensure clarity and maintainability.

What are the defined types for conventional commits?▼

Defined types for conventional commits include `feat` for features, `fix` for bug fixes, and `refactor` for code refactoring. Type selection can also adapt based on your specific development workflow, such as TDD.

How do I determine the correct scope for my git commit?▼

Determining the correct scope for a git commit involves applying specific derivation strategies provided by the skill. Scopes help categorize the impact of changes within your project structure for better maintainability.

Why use conventional commits for version control?▼

Using conventional commits for version control facilitates a consistent and machine-readable commit history. This standardization makes it easier to track changes, generate changelogs, and maintain code quality across development projects.

Are there best practices for the description in a conventional commit?▼

Yes, description best practices require writing concise and descriptive commit summaries. Following these rules ensures the commit message clearly communicates the changes for improved maintainability.

Related Skills

Explore More Software Engineering Skills→
bitsocialnetbitsocialnet
1

commit

Generates logical, formatted git commits from analyzed diffs and predefined scopes.

Official
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

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

Community
Intermediate
mezivillagermezivillager
1

git-operations

Validate Git commit messages against Conventional Commits and branch rules.

Community
Intermediate
taiga-Ktaiga-K
1

create-commit

Generate Conventional Commits with Japanese subject and body from diffs.

Community
Intermediate