git-commit

Generate single-line Git commit messages in conventional `type: description` format.

Updated Aug 27, 2026

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

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you generate clear, concise, and conventionally formatted Git commit messages, improving the readability and maintainability of your project's history.

Core Features & Use Cases

Conventional Commits: Adheres to a standardized format (type: description) for commit messages.
Concise Summaries: Focuses on a single line, suitable for quick understanding.
Use Case: After making changes to a feature, use this Skill to generate a commit message like feat: Add user authentication module.

Quick Start

Use the git-commit skill to write a git commit message for a new feature.

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 my code changes?▼

To write a conventional commit message, summarize your code changes using the format `type: description`, utilizing types like `feat`, `fix`, or `refactor` to categorize the update.

What is the character limit for a conventional commit description?▼

The conventional commit description has a 50-character limit, ensuring the single-line summary remains concise and readable for version control history.

Can I generate a single-line Git commit summary for a new feature?▼

Yes, you can generate a single-line Git commit summary for a new feature by applying the `feat` type prefix, resulting in a message like `feat: Add user authentication module`.

What conventional commit types are supported for version control?▼

Supported conventional commit types for version control include `feat`, `fix`, `refactor`, `chore`, `docs`, `test`, and `ci`, allowing standardized categorization of repository changes.

Does this tool generate multi-line Git commit messages with body text?▼

No, this approach focuses exclusively on generating a single-line Git commit message and does not produce multi-line body text or detailed descriptions.

Why use conventional commits for summarizing code changes?▼

Using conventional commits improves the readability and maintainability of your project history by enforcing a standardized `type: description` format for all version control updates.