git-commit

Generate Git commit messages following Conventional Commits and Gitmoji standards.

3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/lucasgrow/some-skills --skill git-commit-lucasgrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/lucasgrow/some-skills/tree/main/git-commit
Command: npx skills add https://github.com/lucasgrow/some-skills --skill git-commit-lucasgrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes Git commit messages, ensuring clarity, consistency, and a visually organized commit history by enforcing Conventional Commits and Gitmoji conventions.

Core Features & Use Cases

  • Conventional Commits: Enforces a structured format for commit messages (type, scope, subject, body, footer).
  • Gitmoji Integration: Encourages the use of emojis to visually categorize commit types.
  • Use Case: When committing a new feature that also includes documentation updates, you can use this skill to generate a commit message like ✨ feat(docs): add new user guide section.

Quick Start

Use the git-commit skill to generate a commit message for a bug fix that closes issue 123.

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 with gitmoji?

A conventional commit message with gitmoji combines a structured format of type, scope, subject, body, and footer with an emoji prefix. This enforces clarity and consistency for your code history.

What is the correct format for conventional commits?

The correct format for conventional commits requires specific structural elements including type, scope, subject, body, and footer. Adhering to these formatting rules ensures a consistent and discoverable commit history for software projects.

How do I generate a git commit message for a bug fix that closes an issue?

To generate a git commit message for a bug fix, you format the output using conventional commits and gitmoji. The resulting message structures the type as a fix and includes the issue closure in the footer.

When should I use gitmoji in my version control history?

You should use gitmoji in your version control history when you want to visually categorize commit types. Incorporating these visual cues through emojis makes your code history more discoverable and visually organized.

Can I include multiple changes like features and documentation in one conventional commit?

Yes, you can include multiple changes like features and documentation in one conventional commit. You can generate a message like a feature commit with a docs scope to accurately represent combined updates.