commit

Create git commits for dotfiles changes grouped by component directories.

284|10|Updated Dec 6, 2015
One-click install
npx skills add https://github.com/meain/dotfiles --skill commit-meain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/meain/dotfiles/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/meain/dotfiles --skill commit-meain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating Git commits for your dotfiles, ensuring consistency and clarity by grouping changes by their respective configuration components.

Core Features & Use Cases

  • Component-Based Committing: Organizes commits around specific dotfile categories (e.g., emacs/, zsh/, home-manager/).
  • Conventional Commits: Adheres to a [component] brief-area: what changed format for easy understanding and parsing.
  • Use Case: After updating your Emacs configuration and tweaking your Zsh prompt, use this Skill to create two distinct, well-described commits: one for Emacs changes and another for Zsh.

Quick Start

Use the commit skill to stage and commit all changes in the emacs directory with the message "Update emacs configuration".

Frequently Asked Questions about commit

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

FAQPage Schema
How do I group dotfiles changes by component for git commits?

To group dotfiles changes by component for git commits, this skill organizes changes by configuration directories like emacs/ or zsh/ and generates structured commit messages. This ensures each commit isolates a specific configuration area.

What is the conventional commit format for dotfiles version control?

The conventional commit format for dotfiles version control follows a `[component] brief-area: what changed` structure. This format categorizes changes by directories like home-manager/ to make configuration history easy to parse and understand.

Do I need stow to manage and commit dotfiles configurations?

Yes, you need stow to manage and commit dotfiles configurations because it handles the symlinking of configuration files. Git is also required to manage the actual version control and create the commits.

How do I create separate git commits for emacs and zsh dotfiles updates?

To create separate git commits for emacs and zsh dotfiles updates, you stage and commit changes by their respective component directories. This generates two distinct commits using the conventional prefix style for each configuration area.

What is the best way to organize dotfiles commit history by configuration area?

The best way to organize dotfiles commit history by configuration area is to group changes by component directories such as emacs/ or zsh/. This approach creates well-described, isolated commits for each specific configuration category.