git-commit

Analyze Git worktree status and group changes into atomic commits.

2|Updated Feb 18, 2021
One-click install
npx skills add https://github.com/jinyongp/dotfiles --skill git-commit-jinyongp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/jinyongp/dotfiles/tree/main/agents/skills/git-commit
Command: npx skills add https://github.com/jinyongp/dotfiles --skill git-commit-jinyongp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of managing complex Git worktrees by intelligently grouping changes into logical, atomic commits while protecting sensitive files and maintaining repository history standards.

Core Features & Use Cases

  • Atomic Grouping: Automatically identifies and separates independent concerns within the same file or across multiple files into coherent commits.
  • Safety Guardrails: Prevents accidental staging of sensitive files like .env or private keys and validates changes against repository hooks.
  • Use Case: When you have multiple unrelated features and bug fixes mixed in your current worktree, use this skill to safely stage and commit them as separate, well-documented commits that follow the project's established style.

Quick Start

Use the git-commit skill to inspect your current worktree and group your pending changes into clean, logical commits.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I group mixed changes into logical atomic git commits?

This skill automates grouping mixed worktree changes into logical atomic git commits by analyzing diffs and separating independent concerns across files into coherent, well-documented commit units.

How can I prevent accidentally committing sensitive configuration files?

You can prevent accidentally committing sensitive configuration files by using this skill's safety guardrails, which block the staging of files like .env or private keys during the automated commit grouping process.

Do I need Git CLI and shell access to automate my commit workflow?

Yes, you need Git CLI and shell access to the repository worktree, because this skill requires direct shell access to perform diff analysis and execute staging and commit operations on your codebase.

What is the best way to separate unrelated features in my current worktree?

The best way to separate unrelated features in your worktree is using automated atomic grouping, which inspects pending changes and stages them as separate commits following your project's established history style.

Can this skill split independent concerns within the same file into separate commits?

Yes, the atomic grouping feature identifies and separates independent concerns within the same file, allowing you to safely stage and commit them as distinct, logically grouped repository changes.