git-commit-crafter

Create atomic, revertable git commits with Conventional Commits messages.

256|5|Updated Jan 24, 2022
One-click install
npx skills add https://github.com/ryoppippi/dotfiles --skill git-commit-crafter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-crafter
Source: https://github.com/ryoppippi/dotfiles/tree/main/claude/skills/git-commit-crafter
Command: npx skills add https://github.com/ryoppippi/dotfiles --skill git-commit-crafter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill eliminates the manual effort and inconsistency in creating high-quality, atomic Git commits. It ensures your commit history is clean, revertable, and adheres to professional standards like Conventional Commits, saving you time and improving code review efficiency.

Core Features & Use Cases:

  • Automated Conventional Commits: Generates commit messages that strictly follow the Conventional Commits specification (type(scope): subject).
  • Atomic Commit Splitting: Analyzes changes and intelligently splits them into the smallest logical, independently revertable units.
  • Detailed Commit Bodies: Ensures each commit includes a comprehensive body explaining WHAT changed, WHY, and HOW, enhancing documentation.
  • Use Case: You've implemented a new feature with several related changes across multiple files. Instead of a single, monolithic commit, use this Skill to automatically produce a series of perfectly structured, atomic commits, each clearly documenting its specific change, making code reviews and future reverts straightforward.

Quick Start: Use the git-commit-crafter skill to commit my recent changes, ensuring they follow Conventional Commits standards and are atomic.

Frequently Asked Questions about git-commit-crafter

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

FAQPage Schema
How do I create atomic commits that are independently revertable?

Atomic commits are the smallest logical units of change that can be reverted independently without breaking code. This Skill analyzes your repository changes and automatically splits them into atomic commits, each addressing a single concern across files, making your history clean and code reviews straightforward.

What are Conventional Commits and why do they matter?

Conventional Commits is a specification for commit messages using the format `type(scope): subject` with structured bodies. They standardize your commit history, enable automated changelog generation, and improve collaboration. This Skill generates commits that strictly follow this standard.

Can I automatically split my changes into multiple well-organized commits?

Yes. This Skill surveys your staged and unstaged changes with git status and git diff, extracts independent hunks, and intelligently stages only intended portions. It produces multiple atomic commits, each with a descriptive body explaining what changed and why.

How do I ensure my commit messages follow professional standards?

This Skill generates commit messages adhering to Conventional Commits format with proper body content wrapped at 72 characters. It also aligns new commits with your project's existing history patterns, ensuring consistency across your repository.

What's the benefit of atomic commits for code reviews?

Atomic commits isolate changes by logical concern, making reviews faster and more focused. Reviewers can understand each commit's purpose independently, and future reverts are surgical—removing only the specific change without collateral damage.

Does this work with version control workflows that require clean history?

Yes. By producing independently revertable commits with standardized messages, this Skill integrates with workflows requiring clean, auditable history—such as feature branches, squash-and-merge pipelines, and release tagging.