commit

name	commit
description	Create a well-formed git commit. Detects the remote host, stages appropriate files, writes a conventional-commit message focused on the why, and never commits secrets. Invoke manually with /commit.
disable-model-invocation	true

/commit

Create a clean commit. Only when the user asks — never commit proactively.

Steps

1. Survey (run in parallel): git status, git diff (unstaged), git diff --staged, and git log --oneline -10 to match the repo's message style.
2. Detect host with git remote -v so terminology and later PR/MR steps align: GitLab → glab world; GitHub → gh world.
3. Draft the message. Conventional commits: feat:, fix:, chore:, refactor:, docs:, test:, perf:. One concise subject line focused on the why; add a short body only if the change isn't self-explanatory.
4. Safety. Never stage .env*, keys, or files under secrets//credentials/. If the user explicitly asks to commit such a file, warn first.
5. Commit. Stage the relevant files, create the commit, then run git status to confirm.
6. If a pre-commit hook modifies files or fails, fix the issue and create a NEW commit (don't blindly --amend).

Guardrails

• Do not push unless the user asks.
• Do not update git config or use interactive (-i) git flags.