git-commit

Draft imperative commit messages for staged or unstaged changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage and commit changes with clean, imperative-mood messages to improve history readability and traceability.

Core Features & Use Cases

  • Imperative commit messages: enforce action-focused messages (e.g., "Fix bug in user login flow").
  • Staged and unstaged changes handling: provides guidance for commits that cover all related changes.
  • Commit discipline: enforces message length limits, bullet-point bodies for multi-change commits, and avoids pushing to remote.

Quick Start

Draft a clean, imperative-mood commit message for the current staged 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 clean git commit message using imperative mood?

To write a clean git commit message, use imperative mood like "Fix bug in user login flow" to enforce action-focused history. Keep the summary under 72 characters and use bullet-point bodies for multi-change commits to improve readability and traceability.

What is the best way to format multi-change commits in version control?

The best way to format multi-change commits is using bullet-point bodies to separate distinct changes. This commit discipline keeps the summary under 72 characters and applies imperative mood to ensure the version history remains readable and traceable.

Can I commit both staged and unstaged changes at the same time?

Yes, you can handle both staged and unstaged changes by drafting a single commit message that covers all related changes. This ensures version control consistency by grouping related modifications into one traceable history entry.

Does drafting a commit message automatically push to the remote repository?

No, drafting a commit message does not push to the remote repository. The commit discipline explicitly prevents pushing to remote, ensuring you only record changes to local version history without triggering any remote updates.

Why should commit messages be limited to under 72 characters?

Commit messages should be limited to under 72 characters to improve history readability and traceability. This length constraint enforces concise summaries, while detailed multi-change information is moved into bullet-point bodies for better version control consistency.