git-commit

name	git-commit
description	Create safe atomic commits with repo-consistent messages.
compatibility	opencode
metadata	{"workflow":"git","audience":"engineers"}

What I do

• Turn working tree changes into one or more atomic commits.
• Infer commit message style from recent history.
• Avoid committing secrets and generated artifacts.

When to use me

• You have local changes and want to commit them safely.
• You want commits split by concern (feature vs fix vs refactor).

Guardrails (non-negotiable)

• Never commit .env, credential files, or tokens.
• Never create empty commits.
• Never bypass hooks (--no-verify) unless the user explicitly asks.
• If a hook modifies files after a commit attempt, include those changes in a NEW commit (no amend unless the user asked and the commit is not pushed).

Workflow

1. Confirm we are inside the intended repo.
2. Inspect state:
   • git status
   • git diff
   • git diff --cached
3. If message style is unknown, infer it:
   • git log -10 --format=%s
4. Stage intentionally:
   • Prefer git add -p (interactive) when possible.
   • If interactive input is not supported, stage by explicit paths.
5. Re-check staged diff:
   • git diff --cached
6. Propose a commit message (1 line subject). Focus on the why.
7. Create the commit.
8. Verify:
   • git status
   • git show --stat

Message guidelines

• Keep subject <= ~72 chars.
• Use the repo’s existing tense/style (derived from git log).
• If the repo uses Conventional Commits, use type(scope): subject.

Questions I should ask if unclear

• “Should I split this into multiple commits (e.g. code vs config)?”
• “What’s the intended base branch (main/master/develop)?”
• “Is Conventional Commits required here?”