commit

Group git changes into focused commits with mandatory gitmojis and conventional-commit structure.

2|Updated Feb 24, 2026

Search Tags:#git #workflow #commit #staging #code-review #gitmoji #conventional-commits

Ready to run

npx skills add https://github.com/skrrt-sh/skills --skill commit-skrrt-sh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/skrrt-sh/skills/tree/main/plugins/ship/skills/commit
Command: npx skills add https://github.com/skrrt-sh/skills --skill commit-skrrt-sh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unmanaged git workflows often produce messy history and missed context. This skill guides the agent to create focused commits that use mandatory gitmojis, improving traceability and review quality.

Core Features & Use Cases

Enforces the conventional-commit workflow with mandatory gitmojis for every commit.
Assists in splitting changes into coherent commits suitable for code review and release notes.
Validates commit headers and bodies to ensure clear, actionable history.

Quick Start

Ask the agent to generate a focused commit with a single, descriptive header and an explanatory body using the gitmoji convention.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I format git commits using conventional commits and gitmoji?▼

Conventional commits with gitmoji require a specific header structure starting with an emoji, followed by a type, scope, and description. This skill validates headers and bodies to ensure your commits are production-ready and clearly documented.

What is the best way to split staged changes into focused commits for code review?▼

Splitting staged changes into focused commits involves grouping related file modifications together. This skill guides you through breaking down diffs into coherent, logical commits that are appropriate for reviews and release notes.

Why use gitmoji in a conventional commit workflow?▼

Gitmoji in a conventional commit workflow improves traceability and review quality by providing visual context. This skill enforces mandatory gitmojis for every commit, ensuring clear and actionable git history.

Can I selectively stage files and generate a commit with a required header and body?▼

Yes, you can apply selective file changes to staging to generate focused commits. This skill enforces required header structure, body content, and optional footers, ensuring commits are production-ready and clearly documented.

Does this conventional commit workflow support optional footers for release notes?▼

Yes, the conventional commit workflow supports optional footers to document breaking changes or metadata. This skill enforces required header structure and body content while guiding you to include optional footers for release-ready commits.

When do I need to group git diffs into coherent commits?▼

You need to group git diffs into coherent commits when unmanaged workflows produce messy history and missed context. This skill solves that by enforcing structured conventional commits that improve traceability and review quality.