commit

Git Commit

Create a clean, well-structured commit. Generic across stacks; add your own project-specific sensitive paths and commit conventions on top of the checks below.

Phase 1: Pre-flight Checks

Run these in parallel to assess the working tree:

git status
git diff --stat
git log --oneline -5

Never use git status -uall on a large repo. It can exhaust memory scanning untracked files.

Sensitive File Scan

Scan the diff and untracked files for:

• .env files, *.pem, *.key, credential files, private keys, API secrets
• Hardcoded secrets or tokens in the diff itself (key = "...", password = "...", connection strings with embedded credentials)
• Scratch/experiment directories that shouldn't ship (_debug/, _test/, or whatever your project uses for throwaway work)

Tell the user to extend this list with their own project's sensitive paths (a secrets directory, a local config file, a vendor-specific credentials format). The checks above are a floor, not a ceiling.

Gating Rules

BLOCK (stop immediately, show what was found):

• .env files or equivalent in the diff
• *.pem, *.key, or other credential files
• A literal secret, API key, or private key hardcoded in a tracked file
• Files inside a scratch/experiment directory

WARN (show the warning, ask to confirm before proceeding):

• Large, unrelated changes spanning many files (suggest splitting into multiple commits)
• A generated or build artifact changed without its source changing (stale build, or someone hand-edited output)
• Leftover debug logging outside scratch dirs (console.log, print, var_dump, dd, or your language's equivalent)

If blocked, explain what was found and stop. Do not stage or commit.

Phase 2: Analyze Changes

Determine commit type from the diff:

Type	When
feat	New feature or capability
fix	Bug fix
refactor	Code restructuring, no behavior change
style	Formatting, whitespace, no logic change
docs	Documentation only
chore	Build, config, dependency, maintenance
perf	Performance improvement, no behavior change
test	Test-only changes