Stage changed files — AI Prompts for Git

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

Stage the files I modified in src/auth, tests/auth, and the migration script…

Stage the files I modified in src/auth, tests/auth, and the migration script 20260714_add_tokens.sql so they’re ready for the next commit. Verify that there are no accidental large binaries staged and that .env and secrets are excluded. Give me the exact list of staged filenames before I commit.

Improve — make it easier to accept

Before I stage my changes, make it easy to review: show diffs for only src/auth and tests/auth,…

Before I stage my changes, make it easy to review: show diffs for only src/auth and tests/auth, highlight any whitespace or formatting-only changes, point out any newly added files larger than 200KB, and warn if a secrets file like .env or keys.json would be staged. That will help me stage exactly what reviewers need to see.

Decide — diagnose the stuck moment

I attempted to stage my changes and noticed a 15MB file new_key_bundle.bin in src/auth that I did…

I see a large added file I didn’t expect.

I attempted to stage my changes and noticed a 15MB file new_key_bundle.bin in src/auth that I did not intend to add. Priya on security will block the PR if that lands and I don’t know whether it’s needed. What’s the most likely reason it’s there and how should I remove it from the staged set without losing the other staged changes?

Become — change the pattern

Our team keeps accidentally staging large or secret files and wasting time rewriting history to…

We repeatedly stage accidental files and then squash to remove them.

Our team keeps accidentally staging large or secret files and wasting time rewriting history to remove them. Which simple habits and pre-stage checks (gitignore hygiene, pre-commit hooks, a small checklist) will stop those accidents and save Priya in security and reviewers time?

Next to this one

Other version control work people do in Git.

Show changes between commits Sign commits or tags Split a commit into multiple Squash commits during rebase Squash multiple commits Stash local changes Submodule add or update Switch to a branch Tag a commit Verify signed commits

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt