git:commit

Create emoji-enhanced conventional commit messages for Git changes.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/luicabref97/sushi-jungle-web --skill git-commit-luicabref97
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git:commit
Source: https://github.com/luicabref97/sushi-jungle-web/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/luicabref97/sushi-jungle-web --skill git-commit-luicabref97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often produce inconsistent, oversized, or unclear commits that slow code review and blur change intent; this Skill enforces conventional commit style and helps keep commits atomic and informative.

Core Features & Use Cases

  • Branch safety: Detects when you're on master or main and offers to create a feature branch using the type/username/description pattern.
  • Pre-commit validation: Runs project linters and build checks by default and respects a --no-verify flag to skip them.
  • Smart commit composition: Inspects git status and diffs, suggests splitting unrelated changes into multiple commits, and generates emoji-enhanced conventional commit messages for each logical change.
  • Use Case: Ideal for feature development, bug fixes, and chore updates where clear commit history, linting, and branch hygiene are required.

Quick Start

Create a conventional commit with emoji for the current changes and run the project's linters before committing unless I specify --no-verify.

Frequently Asked Questions about git:commit

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

FAQPage Schema
How do I create conventional commit messages with emoji for my git changes?▼

To create conventional commit messages with emoji for git changes, this Skill inspects your git status and diffs, generates emoji-enhanced messages for each logical change, and stages and commits them atomically.

Can I run pre-commit linting checks before staging my git changes?▼

Yes, you can run pre-commit linting checks before staging your git changes; the Skill runs project linters via pnpm, yarn, npm, or bun by default and respects a --no-verify flag to skip validation.

How do I split unrelated git diffs into separate atomic commits?▼

To split unrelated git diffs into separate atomic commits, the Skill inspects your working tree, suggests splitting complex diffs into multiple logical changes, and generates a distinct conventional commit message for each one.

Does this Skill prevent committing directly to the master or main branch?▼

Yes, this Skill prevents committing directly to the master or main branch by detecting your current branch and offering to create a new feature branch using a type/username/description naming pattern.

What is the best way to automate branch naming and commit formatting in local git repositories?▼

The best way to automate branch naming and commit formatting in local git repositories is using a Skill that enforces a type/username/description branch pattern and generates emoji-enhanced conventional commits automatically.