commit

Generate conventional git commits with emoji prefixes and atomic split detection.

Updated Mar 30, 2026

Search Tags:#code quality #git #version control #commit #conventional commits

Ready to run

npx skills add https://github.com/Eric-Pacheco95/claude-workbench --skill commit-eric-pacheco95

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Eric-Pacheco95/claude-workbench/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Eric-Pacheco95/claude-workbench --skill commit-eric-pacheco95

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures clean, well-structured git commits by applying the conventional commit format with emoji prefixes. It analyzes staged changes, helps in splitting them into atomic commits if necessary, and writes clear messages explaining the commit's purpose.

Core Features & Use Cases

Conventional Commit Format: Adheres to the standard commit message format for clarity and consistency.
Atomic Commit Detection: Suggests splitting large commits into smaller, more manageable pieces.
Message Explanation: Encourages writing commit messages that explain the "why" behind each change.
Use Case: Before merging a feature branch, use this Skill to review and finalize your commits for a clean and well-documented codebase.

Quick Start

Create a commit for the 'fix the data validation bug' using the commit skill.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I write conventional git commits with emoji prefixes?▼

Atomic commit detection analyzes staged changes to identify distinct logical modifications, suggesting you split large commits into smaller pieces. This process keeps your repository history clean by ensuring each commit represents a single, manageable update.

What is the best way to split large git commits into atomic pieces?▼

Conventional git commits with emoji prefixes are generated by analyzing staged changes and formatting the message with standard types, scopes, and corresponding emojis. This ensures commit messages are visually identifiable and structurally consistent across the repository history.

How do I ensure my git commit messages explain the purpose of the changes?▼

Commit message explanations are enforced by prompting you to detail the 'why' behind each staged change, moving beyond simple descriptions. This generates clear git commit messages that provide essential context for future codebase maintenance.

Can I use conventional commit format to review changes before merging a feature branch?▼

You can use conventional commit formatting to review and finalize changes before merging a feature branch. This workflow analyzes your staged changes to ensure the codebase remains well-documented and cleanly structured for version control.

Do I need to stage my git changes before generating a conventional commit?▼

You need to stage your git changes before generating a conventional commit because the process analyzes the staged diff. This staged analysis drives the atomic split detection and ensures the suggested commit message accurately reflects the included modifications.