git-commit

Review current changes and commit them with Conventional Commits formatted messages.

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/mjun0812/skills --skill git-commit-mjun0812
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/mjun0812/skills/tree/main/skills/git/git-commit
Command: npx skills add https://github.com/mjun0812/skills --skill git-commit-mjun0812

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing consistent, well-structured commit messages is tedious and often skipped, leading to messy git histories. This Skill inspects your staged and unstaged changes, generates a Conventional Commits compliant message, and commits for you. ## Core Features & Use Cases - Automatic Staging Detection: Checks for staged changes first; if none exist, it reviews and stages current changes before committing. - Conventional Commits Format: Generates messages following the <type>: <description> specification with bulleted body lines, one change per line. - Multi-language Messages: Writes commit messages in the language you specify (e.g., "ja" or "en"), defaulting to English, with correct style conventions per language. - Use Case: After finishing a bug fix, invoke the Skill to have it review the diff, produce a message like fix: prevent racing of requests with a detailed body, and commit it without pushing. ## Quick Start Review my current changes and commit them with a Conventional Commits message in English.

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 Conventional Commits message automatically?

Invoke this Skill after making changes; it reads the staged and unstaged diffs, then generates a message in the format `<type>: <description>` with a bulleted body and runs git commit. No manual message writing is needed.

Does this Skill stage my changes before committing?

It only stages changes if nothing is already staged. If staged changes exist, it commits them as-is without adding more files, preserving your intentional staging choices.

Can I generate git commit messages in Japanese or other languages?

Yes, pass a language argument such as "ja" or "en". Japanese messages use noun-ending style without desu/masu, while English messages use imperative fragments. English is the default.

Does git-commit push to the remote repository?

No, the Skill only creates a local commit and never runs git push. You remain in control of when and where commits are published.

What happens if there are no changes to commit?

If neither staged nor unstaged changes exist, the Skill reports that there is nothing to commit and stops without running git commit.