git-commit

Generate Git commit messages following the conventional commits specification.

Updated Feb 8, 2026

Search Tags:#git #version control #commit #conventional commits #code management

Ready to run

npx skills add https://github.com/bresends/skills --skill git-commit-bresends

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/bresends/skills/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/bresends/skills --skill git-commit-bresends

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create well-formatted and informative Git commit messages according to conventional commit standards, ensuring consistency and clarity in your project's history.

Core Features & Use Cases

Conventional Commits: Adheres to a standardized format for commit messages (type, scope, subject, body).
Scope Derivation: Automatically suggests or helps derive the appropriate scope for your commit.
Type Guidance: Provides a clear list of commit types and their intended use.
Use Case: When you've finished a new feature, use this skill to generate a feat(module): subject commit message, explaining the change and its reasoning.

Quick Start

Use the git-commit skill to create a commit message for a new feature in the authentication module.

Frequently Asked Questions about git-commit

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

FAQPage Schema

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

To write a conventional commit message for a new feature, use the format `feat(scope): subject`. This structure includes the type, an optional scope for the module, and a concise subject to ensure your Git history remains clear and discoverable.

What are the different types of conventional commits I can use?▼

Conventional commits include types like feat, fix, refactor, docs, style, test, chore, perf, and ci. Each type categorizes the nature of your Git changes, helping maintain a structured and easily discoverable project history.

How do I add a scope and body to my Git commit message?▼

You add a scope by placing it in parentheses before the subject, like `fix(auth): subject`. The body follows the subject, separated by a blank line, providing additional context and reasoning for the code management change.

When do I need to use the conventional commits specification?▼

You need the conventional commits specification when you want to standardize Git commit messages. It ensures consistency across your software development project, making the version control history informative and automatically discoverable.

Can I automatically generate a commit message for an authentication module update?▼

Yes, you can automatically generate a commit message for an authentication module update. The skill suggests the appropriate scope and type, such as `feat(auth): subject`, to explain the change and its reasoning.