git-commit

name	git-commit
description	Generate a well-formatted Git commit message based on staged changes. Use when the user wants to commit code and needs a clear, conventional commit message written for them.

Git Commit

Generate a commit message for the current staged changes.

Steps

1. Run git diff --cached to see what is staged.
2. If nothing is staged, run git status and tell the user to stage files first.
3. Analyze the diff: identify what changed, why it likely changed, and what component/scope is affected.
4. Write a commit message following the Conventional Commits format:

<type>(<scope>): <short summary>

<optional body: what and why, not how>

Types: feat, fix, refactor, chore, docs, test, style, perf, ci

Rules:

• Summary line: max 72 chars, imperative mood ("add" not "added")
• Scope: the module, file, or feature area affected (optional but preferred)
• Body: only when the change needs context beyond the summary

5. Show the commit message to the user and ask for confirmation or edits.
6. Once confirmed, run git commit -m "<message>" (or with -m for body if needed).