git-commit

Generate Gitmoji-prefixed Conventional Commits from staged diffs.

3|1|Updated Jun 14, 2021

Search Tags:#automation #git #versioning #commits #code-review #gitmoji #conventional-commits

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you generate standardized git commits automatically using Gitmoji prefixed messages and Conventional Commits, ensuring consistency across a project.

Core Features & Use Cases

Generate Gitmoji-prefixed commit messages that follow Conventional Commits based on the diffs you staged.
Validate subject length and formatting rules to ensure alignment with project standards.
Provide examples and guidance for different commit types (feat, fix, docs, etc.) and how to structure scopes.

Quick Start

To create a compliant commit, provide the changes you want to record and let the tool format the message.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I generate conventional commits automatically from staged diffs?▼

To generate conventional commits automatically, this skill translates your staged git diffs into semantically meaningful messages. It formats staged changes into compliant commit messages using Gitmoji prefixes and conventional commit types like feat or fix.

What is the best way to add Gitmoji prefixes to git commit messages?▼

Adding Gitmoji prefixes to git commit messages is automated by translating staged changes into standardized emoji mappings. This ensures your project maintains visual consistency across conventional commit types without manual emoji lookups.

How do I validate subject length and formatting rules for conventional commits?▼

To validate subject length and formatting rules for conventional commits, the skill checks your generated messages against project standards. It enforces validation rules on the subject length, allowed types, and scope structure before finalizing the commit.

Can I include breaking changes and scopes in my automated conventional commits?▼

Yes, you can include breaking changes and optional scopes in your automated conventional commits. The skill structures semantically meaningful commits by applying optional scope parameters and breaking change indicators based on the staged diffs.

Does this skill require integration with a local git environment to work?▼

Yes, this skill requires integration with a local git environment to function correctly. It needs access to your staged diffs to translate code changes into validated, Gitmoji-prefixed conventional commit messages.

What are the limitations of automating conventional commits with Gitmoji?▼

Limitations of automating conventional commits with Gitmoji include strict validation of allowed types and subject length constraints. The automation relies entirely on accurately staged diffs and predefined emoji mappings, limiting custom message formats outside standard conventions.