Commit

Stage pending changes and create a single commit with a concise, accurate message.

Process

1. Gather context. Run these in parallel:

   • git status — list changed and untracked files
   • git diff HEAD — see actual content changes
   • git branch --show-current — confirm branch
   • git log --oneline -5 — learn the repo's commit message style

2. Run safety checks before staging.

   • If the current branch is main, master, or develop, stop and ask the user whether to proceed. Feature branches are the default.
   • Scan the file list for secrets or stray binaries: .env, .env.*, credentials*, *.key, *.pem, id_rsa*, or any file larger than 5 MB. If any match, stop and confirm with the user before staging.

3. Stage files explicitly by name. Never use git add . or git add -A.

   • Example: git add src/foo.ts src/bar.ts tests/foo.test.ts
   • Include both modified and new files that belong in the commit.