git-commit-executor

Analyze git changes and create logical Conventional Commits.

Updated Jan 6, 2026

Search Tags:#automation #git #version-control #conventional-commits #diff-analysis #commit-management

Ready to run

npx skills add https://github.com/yamato0811/my-agent-skills --skill git-commit-executor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit-executor
Source: https://github.com/yamato0811/my-agent-skills/tree/main/skills/git-commit-executor
Command: npx skills add https://github.com/yamato0811/my-agent-skills --skill git-commit-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes code changes, breaks them into logical commits, and applies Conventional Commits to actually perform the commits.

Core Features & Use Cases

Logical commit grouping: Automatically splits related changes into single commits.
Conventional Commit messages: Generates messages in the <type>(<scope>): <subject> format.
Selective staging & execution: Stages only the targeted changes before committing and ensures correct commit order.

Quick Start

Use this Skill to automatically turn work-in-progress changes into properly scoped, atomic commits by executing git add on relevant files and git commit with Conventional Commit messages.

Frequently Asked Questions about git-commit-executor

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

FAQPage Schema

How do I automatically split work-in-progress git changes into atomic commits?▼

To split work-in-progress git changes into atomic commits, this Skill inspects git status and diffs to group related modifications, selectively stages them with git add, and creates logical commits in a deliberate order.

How does conventional commit automation work for staged and unstaged files?▼

Conventional commit automation works by analyzing your current diffs, grouping related file changes by feature or bug fix, selectively staging only those related changes, and generating messages in the <type>(<scope>): <subject> format.

Can I generate conventional commit messages automatically from my git diff?▼

Yes, you can generate conventional commit messages from your git diff. This Skill inspects staged and unstaged changes, stages only targeted files with git add, and creates properly formatted messages before executing the commit.

What is the best way to group related file changes into separate commits?▼

The best way to group related file changes into separate commits is to use an automated diff analysis tool. This Skill inspects your changes, stages related modifications selectively, and commits them in a deliberate order.

Does this automated commit tool support selective staging for mixed feature and bug fix changes?▼

Yes, this automated commit tool supports selective staging for mixed changes. It inspects git status and diffs to isolate feature updates, bug fixes, refactors, or documentation changes, staging only the targeted files before each commit.

When should I not use automated conventional commits for version control?▼

You should not use automated conventional commits when your workflow requires manual control over commit grouping or message phrasing. The tool enforces granular commits based on diff analysis, which may override custom staging preferences.