commit

Generates conventional commit messages from staged Git diffs with emojis, types, and scopes.

2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/SukbeomH/HExoskeleton --skill commit-sukbeomh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/SukbeomH/HExoskeleton/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/SukbeomH/HExoskeleton --skill commit-sukbeomh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of well-formatted Git commits, ensuring consistency and adherence to conventional commit standards, while also helping to split complex changes into atomic units.

Core Features & Use Cases

  • Conventional Commits: Generates commits using the <emoji> <type>(<scope>): <description> format.
  • Atomic Commits: Analyzes diffs to suggest splitting large changes into smaller, logical commits.
  • Use Case: After completing a new feature and its tests, use this skill to generate a feat commit for the code and a separate test commit for the tests, ensuring a clean and understandable Git history.

Quick Start

Use the commit skill to analyze staged changes and create a conventional commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from staged Git diffs?

This Skill analyzes staged Git diffs to generate conventional commit messages automatically, appending appropriate emojis, types, and scopes to ensure strict formatting.

What is an atomic commit and how do I split logical changes into them?

Atomic commits isolate single logical changes. This Skill analyzes staged diffs and suggests splitting complex changes into smaller, independent atomic commits following the HXSK protocol.

How do I separate code and test files into different Git commits?

To separate code and tests, the atomic commit feature analyzes staged changes and generates a distinct feat commit for source code and a separate test commit for test files.

Does this conventional commit generator work without any external dependencies?

Yes, this conventional commit generator operates without external dependencies, relying on internal scripts and references to analyze diffs and enforce strict formatting rules.

What is the correct format for conventional commits with emojis and scopes?

The correct format is <emoji> <type>(<scope>): <description>. This Skill applies that structure automatically to maintain a clean and understandable Git history.