kenoxa/commit

Stage only in-scope files, draft Conventional Commits message, confirm with user, commit.

Workflow

1. Inspect — git status + git diff --stat to see dirty files.
2. Scope files — priority order:
   • User-specified files (highest)
   • Files attributable to current task/session
   • Best-guess from dirty files — include proposed list in confirmation step
3. Draft message — <type>[optional scope][!]: <description> (imperative, specific, concise, no trailing punctuation; prefer ≤72 chars total). Add body only when it adds non-obvious context. Omit if subject fully captures the change. Body: blank line after subject; explain why, constraints, or impact; do not restate subject or diff; wrap at 72 chars.
4. Confirm — display proposed message as fenced code block + staged file paths. Ask one concise question. Never commit without explicit user approval.
5. Commit — stage only confirmed paths. If committed paths differ from staged (e.g., hooks modified content), report deltas.
6. Report — commit hash and summary.

Scoped Staging

Never auto-stage all dirty files (git add -A / git add .). Stage only confirmed in-scope paths. Pre-commit hooks may modify content during commit — expected.

Message Format

Conventional Commits. Types: feat, fix, refactor, chore, docs, test, perf, ci, build.

• Subject: imperative, specific, no vague summaries (update stuff, fix things)
• Subject: lowercase Conventional Commit prefix; do not force capitalization
• Body: explains why, not what — diff shows what changed
• Body: omit unless useful; no repetition from subject
• Breaking changes: ! suffix on type or BREAKING CHANGE: footer

Constraints

• Push only when explicitly requested.
• Amend only when explicitly requested.
• No in-scope committable files → report and stop.
• Never strip or modify commit trailers added by platform or user.

Anti-Patterns

• Auto-staging all dirty files without scoping
• Committing without explicit user confirmation
• Vague commit messages
• Pushing or amending without being asked