skills.rest
k-negishi
k-negishiCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Analyze diffs and generate prefixed Git commit messages.

1|Updated Nov 8, 2025
Search Tags:#git#versioning#commit#best-practices#message#prefix
One-click install
npx skills add https://github.com/k-negishi/calendar-auto-register --skill git-commit-k-negishi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/k-negishi/calendar-auto-register/tree/main/.claude.bk/skills/git-commit
Command: npx skills add https://github.com/k-negishi/calendar-auto-register --skill git-commit-k-negishi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git commit quality is often inconsistent, leading to vague messages and difficult history tracking.

Core Features & Use Cases

  • Analyze diffs across files and determine the most appropriate commit prefix (add, fix, docs, refactor, test, chore, perf, build, ci, revert, style).
  • Generate clear, actionable commit messages that reflect the exact changes and rationale.
  • Support multi-change scenarios by recommending split points and grouping related edits for atomic commits.

Quick Start

Analyze the current changes and generate a clear, prefix-appropriate Git commit message ready to apply.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate a properly prefixed git commit message from multiple file changes?▼

To generate a properly prefixed git commit message, analyze the diffs across multiple changed files to determine the correct prefix, such as fix or refactor, and produce a single, clear message reflecting the exact changes and rationale.

What is the best way to split a git commit history when an edit spans multiple concerns?▼

The best way to split a git commit is to analyze the multi-change scenario across files, identify logical split points, and group related edits together to create atomic commits for better history clarity.

When do I need to use specific prefixes like chore, perf, or build in my commit messages?▼

You need to use prefixes like chore, perf, or build when your code changes specifically address maintenance tasks, performance improvements, or build system modifications, ensuring the commit type is immediately recognizable.

Does this approach work for any codebase with inconsistent versioning and diff tracking?▼

Yes, this approach works for any codebase with inconsistent versioning by analyzing the current diffs and applying standardized prefixes to generate clear, actionable commit messages that resolve vague history tracking.

Why should I use a structured prefix for my commit messages instead of just describing the changes?▼

You should use a structured prefix for commit messages because it solves the problem of inconsistent quality, making vague history tracking significantly easier and improving overall project maintainability.

Related Skills

Explore More Software Engineering Skills→
t-miura-024t-miura-024

mt-check-git-diff

Analyze git repository changes and retrieve detailed diffs for modified files.

Community
Intermediate
iludeilude
8

git-workflow

Validate Git commits for secrets and enforce safe push rules.

Community
Intermediate
rito528rito528
1

ensure-branch

Validate and switch Git branches before commits and pull requests.

Community
Intermediate
eglenn-deveglenn-dev
1

commit

Generate git commit messages from status, diff, and log.

Community
Basic