git-commit

Stage working tree changes and generate WHY-focused commit messages.

4|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/motoki317/dotfiles --skill git-commit-motoki317
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/motoki317/dotfiles/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/motoki317/dotfiles --skill git-commit-motoki317

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage meaningful changes and craft commits with WHY-focused messages to clearly justify the rationale behind each update, improving traceability and team understanding.

Core Features & Use Cases

  • Stage meaningful diffs by reviewing changes before committing.
  • Generate WHY-focused messages that clearly explain the rationale for the change.
  • Use Case: When fixing a bug or implementing a feature, ensure the commit has a narrow scope and a WHY-focused message.

Quick Start

Tell the AI to prepare a WHY-focused commit message after staging your changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write a git commit message that explains the rationale behind the change?

A WHY-focused git commit message documents the rationale and intent behind your staged changes rather than just listing what changed. This approach improves project history traceability and team collaboration by clearly justifying each update.

How do I stage meaningful diffs and generate a commit message automatically?

To stage meaningful diffs and generate a commit message, review your working tree changes before committing, then ask the AI to generate a WHY-focused message. This enforces test and lint checks where available to ensure code quality and narrow scope.

Does this commit generation workflow enforce tests and lint checks?

Yes, the workflow enforces test and lint checks where available to ensure commit quality. It applies to code changes across repositories and CI contexts, verifying quality before producing a concise, contextual commit message.

What's the best way to improve project history and collaboration with commit messages?

The best way to improve project history and collaboration is using WHY-focused commit messages that clearly justify the rationale for each update. This ensures commits have a narrow scope and document the intent behind fixes or feature implementations.

Can I use this commit workflow across different repositories and CI contexts?

Yes, you can use this commit workflow across different repositories and CI contexts. It applies to code changes universally, enforcing test and lint checks where available to ensure commit quality regardless of the project environment.