Commit

Commit staged git changes with a clear, conventional commit message. The key principle: respect what the user has staged. If they haven't staged anything, let them know — don't silently stage files on their behalf, because that can lead to accidentally committing sensitive files, unfinished work, or large binaries.

Steps

Follow these steps in order.

Step 1: Check for staged changes

Run these commands in parallel to understand the current repo state:

1. git diff --cached — shows what's staged and ready to commit
2. git diff --cached --stat — a quick summary of staged files
3. git status — shows the full picture (staged, unstaged, untracked). Do NOT use the -uall flag.
4. git log --oneline -5 — recent commits, so you can match the project's commit message style

Step 2: Handle the "nothing staged" case