git-commit

Create atomic git commits with messages matching project conventions.

10|2|Updated Sep 28, 2015
One-click install
npx skills add https://github.com/abatilo/vimrc --skill git-commit-abatilo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/abatilo/vimrc/tree/main/skills/git-commit
Command: npx skills add https://github.com/abatilo/vimrc --skill git-commit-abatilo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual git commit message formatting, ensuring atomicity, and following project conventions can be time-consuming and error-prone. This skill automates the process of creating high-quality, logically grouped, and well-formatted git commits.

Core Features & Use Cases

  • Atomic Commit Creation: Guides you to create single-purpose commits, leveraging git add -p for fine-grained control.
  • Automated Style Detection: Analyzes recent commit history to automatically detect and apply conventional commit standards (e.g., feat:, fix:) or other project-specific formatting.
  • Best Practice Enforcement: Ensures commit messages adhere to best practices like subject line length, imperative mood, and clear separation of subject from body.
  • Use Case: You've made several changes across multiple files. Use this skill to interactively stage related changes and generate perfectly formatted, atomic commits that align with your team's existing Git history.

Quick Start

Use the git-commit skill to stage my current changes and create a series of atomic commits, ensuring each commit message follows the project's existing conventional commit style.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create atomic git commits from multiple file changes?

Atomic git commits group logically related changes into single-purpose units. This skill stages related modifications across files and generates commits with properly formatted messages, using git add -p for fine-grained control to split changes into focused, reviewable units aligned with your project's conventions.

How can I automatically detect and apply my project's commit message style?

Commit message style detection analyzes your recent git history to identify and apply conventions like feat:, fix:, or project-specific formats. This skill inspects existing commits and generates new messages matching detected patterns, ensuring consistency without manual formatting.

What's the best way to ensure commit messages follow team standards?

Best practice enforcement validates subject line length, imperative mood, and clear subject-body separation against conventional commit standards. This skill applies these rules automatically during commit generation, catching formatting issues before they reach version control.

Can I use this for bug fixes, features, documentation, and refactors in one workflow?

Yes, this skill handles multiple change types across various scenarios. It identifies the nature of your changes, stages them appropriately, and generates commits with messages matching your project's conventions for bug fixes, features, docs, and refactors.

How do I avoid committing unrelated changes together?

Interactive staging with git add -p lets you select specific hunks within files, separating unrelated modifications. This skill guides you through partial adds to create truly atomic commits where each change serves a single logical purpose.