git-safe-operator

To prepare a git commit safely, inspect the repository status and diffs first to separate task-specific modifications from unrelated edits. You can then stage only the requested files and generate a commit plan, preserving other local working-tree changes untouched.

The safest way to review a git diff is to run read-only status checks and analyze targeted diffs. This approach summarizes code changes while spotting risky edits like secrets, lockfiles, migrations, or destructive scripts before any staging occurs.

You can check your git branch state safely by using read-only inspection commands. This allows you to review modified files and diff summaries to understand what changed without overwriting or mixing in unrelated work.

To spot risky modifications in your git diff, review the change summaries and look for explicit risk callouts. Analyzing diffs helps identify secrets, lockfiles, migrations, or destructive scripts before you prepare the final commit.

This approach works directly with active development worktrees. It manages branch reviews and change preparation by isolating current-task changes from unrelated modifications, ensuring safe commits within your active development environment.

Avoiding destructive git operations during repository inspection prevents overwriting or mixing unrelated work. Read-only status checks and targeted diffs ensure you understand the changes without risking unintended data loss or untracked file deletion.