git-commit-agent

Analyzes staged git changes and creates a conventional commit message.

2|Updated Sep 25, 2011
One-click install
npx skills add https://github.com/pokutuna/dotfiles --skill git-commit-agent-pokutuna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-agent
Source: https://github.com/pokutuna/dotfiles/tree/main/claude/skills/git-commit-agent
Command: npx skills add https://github.com/pokutuna/dotfiles --skill git-commit-agent-pokutuna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-formatted commit messages is tedious and often inconsistent across a repository. This Skill inspects your staged changes and produces a single conventional commit that matches your repository's existing style. ## Core Features & Use Cases - Diff-Driven Commit Messages: Reads git diff --cached and recent commit history to generate an accurate type(scope): subject message. - Style Matching: Uses your recent commits as a style reference for language, tone, and length, including Japanese/English spacing conventions. - Safe Staging Boundaries: Commits only already-staged files and never runs git add, --amend, or path-based commits, so unrelated work stays untouched. - Use Case: After staging a bug fix with git add, invoke the Skill to produce a commit like fix: correct nil handling in parser without writing the message yourself. ## Quick Start Stage the files you want to commit, then ask the agent to create a conventional commit from the staged changes.

Frequently Asked Questions about git-commit-agent

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

FAQPage Schema
How do I generate a conventional commit message from staged changes?▼

Stage your files with git add, then invoke the Skill. It reads git diff --cached and recent commit history to produce a single commit in type(scope): subject format that matches your repository's existing style.

What commit types does conventional commit format support here?▼

The Skill uses a fixed set of types: feat, fix, docs, refactor, perf, test, chore, deps, tweak, nit, and wip. It picks the most significant type when multiple apply and defaults to chore for miscellaneous updates.

Will it commit unstaged or untracked files automatically?▼

No. The Skill commits only already-staged files and never runs git add, git commit -a, or --amend. If it notices unstaged leftovers, it mentions them in its reply instead of committing them.

What happens if nothing is staged when I run it?▼

The Skill reports that nothing is staged and exits without creating a commit. Staging is the caller's responsibility since the agent lacks the conversation context to judge which files belong together.

Does it decide the commit scope automatically?▼

Scope is omitted by default and only added when it names a genuine area of the repo, such as a monorepo package or infrastructure module. It never invents scopes or copies feature-name scopes from history.