Smart Commit

Safety rules (always)

• Never commit secrets. Before committing, scan the staged diff for things like API_KEY=, sk-, -----BEGIN, password =, .env files. If found, stop and tell the user.
• Never git push --force, reset --hard, or rewrite history unless the user explicitly asks.
• Never commit without showing the user the plan first if there are >1 commits or unrelated changes.

1. Look at what changed

git status --short
git diff --stat
git diff            # and git diff --staged

Read the actual diff — messages are written from the code, not from file names.