# Commit Helper > Guide users through creating meaningful, well-structured git commits following best practices. Use this skill when users want to commit changes, ask for help with commit messages, or need guidance on what to commit. Ensures commits are atomic, descriptive, and follow conventional commit standards. - Skill: `majiayu000/commit-helper-2` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds add majiayu000/commit-helper-2` - Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/commit-helper-2/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: majiayu000 (https://skillmd.com/u/majiayu000) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/majiayu000/commit-helper-2 --- # Commit Helper This skill helps you create high-quality git commits by systematically analyzing changes, crafting meaningful commit messages, and following industry best practices. ## When to Use This Skill Activate this skill when: - User asks to "commit changes" or "create a commit" - User requests "help with commit message" - User says "what should I commit?" or "how should I organize these changes?" - Multiple files have been changed and commits need to be organized - User wants to follow best practices for git commits ## Core Principles ### Atomic Commits - One logical change per commit - Each commit should be independently deployable - If you can describe a commit with "and", it should be split ### Meaningful Messages - Explain WHY, not just WHAT - Use present tense ("Add feature" not "Added feature") - Be specific and concise - First line: 50 chars or less summary - Optional body: detailed explanation with 72 char lines ### Conventional Commits Follow the [Conventional Commits](https://www.conventionalcommits.org/) specification when appropriate: - `feat:` New feature - `fix:` Bug fix - `docs:` Documentation only - `style:` Formatting, missing semi colons, etc. - `refactor:` Code restructuring without behavior change - `perf:` Performance improvements - `test:` Adding or updating tests - `chore:` Maintenance tasks, dependencies, etc. - `ci:` CI/CD changes ## Commit Analysis Process Follow these steps systematically: ### 1. Review Current State ```bash # Check what's staged vs unstaged git status # See staged changes git diff --staged # See unstaged changes git diff # Review recent commits for context git log --oneline -5 ``` ### 2. Analyze Changes Group changes by: - **Type**: Feature, fix, refactor, docs, etc. - **Scope**: Which component/module affected - **Impact**: Breaking changes, minor changes, patches - **Independence**: Can changes be separated? ### 3. Determine Commit Strategy **Single Atomic Commit** - Use when: - All changes relate to one logical task - Changes are interdependent - It's a small, focused change **Multiple Commits** - Use when: - Changes span multiple concerns - Some changes are independent - Mixing features with fixes - Large refactoring with multiple steps ### 4. Stage Strategically ```bash # Stage specific files git add file1.js file2.js # Stage parts of a file interactively git add -p filename.js # Stage all changes of a certain type git add *.test.js ``` ### 5. Craft Commit Message **Format:** ``` ():