git-commit

Group related file changes into focused git commits with generated messages.

1|Updated Aug 26, 2024
One-click install
npx skills add https://github.com/raghavpillai/dotfiles --skill git-commit-raghavpillai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/raghavpillai/dotfiles/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/raghavpillai/dotfiles --skill git-commit-raghavpillai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the git commit workflow by guiding users to group related changes, avoid messy commits, and enforce push after review.

Core Features & Use Cases

  • Group related file changes into focused commits to improve history readability and code reviews.
  • Automatically generate consistent, descriptive commit messages with gencommit, then commit each group.
  • After all groups are committed, push the changes to the remote repository for a smooth release workflow.

Quick Start

Review your working tree, group related changes, let gencommit generate messages and commit each group, then push.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I group multi-file changes into focused git commits?

To group multi-file changes into focused git commits, you review your working tree, logically group related file modifications, and commit each set individually. This approach improves history readability and streamlines code reviews on feature branches.

What is the best way to generate descriptive commit messages automatically?

The best way to generate descriptive commit messages automatically is to use a generation tool like gencommit after grouping your file changes. This ensures consistent, meaningful messaging for each logical set before you push to the remote repository.

How does grouping changes by logical sets improve version control history?

Grouping changes by logical sets improves version control history by separating unrelated modifications into distinct, focused commits. This structured messaging makes history easier to read and helps reviewers understand the specific purpose of each change.

Can I enforce a git status check before grouping commits on a feature branch?

Yes, you can enforce a git status check before grouping commits on a feature branch. The workflow requires reviewing your working tree status first, ensuring all modifications are accounted for before you group and commit changes.

When do I need to push changes after committing grouped file modifications?

You need to push changes after committing grouped file modifications once all logical sets are committed. This final push action sends the structured commit history to your remote repository, completing the release workflow.