Configure user name and email — AI Prompts for Git

2 ready prompts

Written for the moment this actually comes up.

Improve — make it easier to accept

Before I update identities on multiple machines, make it clear to code reviewers: list where name…

Before I update identities on multiple machines, make it clear to code reviewers: list where name and email are set (global, system, local), surface any mismatches between my laptop and CI, and flag if commits already pushed use a different email that would break attribution. Suggest commands to correct past commits if needed.

Become — change the pattern

I repeatedly run into projects where my commit email is inconsistent, causing bot reports and…

Across projects my commit email differs and bots flag me as unknown

I repeatedly run into projects where my commit email is inconsistent, causing bot reports and permission issues. Where am I losing time and credibility, and what single configuration habit or small automation will prevent mismatched identities across machines and CI agents? Include a plan to reconcile already-mislabeled commits with minimal disruption.

Next to this one

Other version control work people do in Git.

Cherry-pick a commit Clone a specific branch Commit staged changes Compare branches Configure ignore rules globally Create a bare repository Create a new branch Create a release or tagger Create and apply a patch Delete a branch locally

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