Git Commit Helper

Analyzes diffs to create atomic conventional commits with parallel git operations.

Updated Sep 11, 2021
One-click install
npx skills add https://github.com/biwsantang/dotfiles --skill git-commit-helper-biwsantang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Git Commit Helper
Source: https://github.com/biwsantang/dotfiles/tree/main/claude/.claude/skills/commit
Command: npx skills add https://github.com/biwsantang/dotfiles --skill git-commit-helper-biwsantang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort and inconsistencies in creating Git commit messages. It ensures your commit history is clean, follows conventional standards, and intelligently suggests splitting changes into atomic commits, saving you time and reducing complexity.

Core Features & Use Cases

  • Intelligent Diff Analysis: Automatically analyzes changes to determine if they should be split into multiple, focused commits.
  • Conventional Commit Formatting: Generates well-structured commit messages (e.g., feat:, fix:) with proper attribution.
  • Use Case: When you've made several changes (e.g., a bug fix, a new feature, and a documentation update) and need to create separate, clean commits without manual effort, ensuring a clear and reviewable history.

Quick Start

Example: Create a new commit with a conventional message

git commit -m "$(cat <<'EOF' feat: add new user profile page

This commit introduces a new user profile page with basic information display. EOF )"

Frequently Asked Questions about Git Commit Helper

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

FAQPage Schema
How do I automatically generate conventional commit messages from my changes?

Conventional commit formatting automatically structures your commit messages with type prefixes like `feat:` and `fix:` based on the changes you've made. This Skill analyzes your diffs and generates properly formatted messages that follow the conventional commits standard, ensuring consistency across your repository history.

Can I split my staged changes into multiple atomic commits automatically?

Yes. Intelligent diff analysis detects when your changes span multiple concerns—such as bug fixes, new features, and documentation updates—and suggests splitting them into separate, focused commits. This keeps each commit atomic and makes your version control history clearer and easier to review.

What does atomic commit mean and why does it matter in version control?

Atomic commits are self-contained changes that address a single concern without mixing unrelated work. They matter because they simplify code reviews, enable precise rollbacks, and make debugging with `git bisect` more effective. This Skill ensures your commits stay atomic by splitting mixed changes automatically.

How do I add Co-Authored-By attribution to my Git commits?

Co-Authored-By attribution is automatically applied during commit creation when multiple contributors have worked on changes. This Skill includes this metadata in your conventional commit messages, properly crediting all authors in your version control history.

Does this work with existing Git workflows and staging?

Yes. This Skill integrates with standard Git operations during commit creation and staging. It performs parallel git operations and smart staging detection, so it works within your existing workflow without requiring changes to how you interact with version control.