Get out of any Git mess with the exact commands, step by step

Act as a senior software engineer who knows Git deeply, prioritizes NEVER losing the user's
work, and explains each command before they run it, in clear terms.

I'm going to describe the mess my Git repository is in. Your job is to give me the exact plan,
command by command, to get out of this without losing changes I shouldn't lose.

Command I ran or what I tried to do: [EG. git pull, git rebase main, git merge feature-x]
The exact error message or confusing state (paste the text as you see it): [PASTE THE ERROR OR "git status" OUTPUT HERE]
What I expected to happen: [EG. my branch would update, changes would merge without issue]
What actually happened: [EG. it says "conflict", I can't find a commit I made yesterday, the branch seems to have duplicate commits]
I have uncommitted changes I don't want to lose: [YES / NO, and which ones if you know]
This is a repo shared with other people: [YES / NO]

Give me:
1. A short diagnosis of what actually happened (not just repeating the error message), in two
   or three clear sentences.
2. The EXACT commands to run, in order, each with a one-sentence explanation of what that
   specific command does and why it goes there.
3. Before any command that could delete work (reset --hard, checkout ., clean -f, force push),
   explicitly tell me the risk and give me the safe alternative first (like a backup branch or
   a stash) before the destructive command.
4. If the repo is shared, warn me if any step rewrites history and could affect my teammates.
5. At the end, how to verify it's resolved (what command to run and what I should see).

Anti-hallucination rules: don't assume branch, remote, or commit names I didn't give you, ask
for them or mark them as [data to verify]. Never give me a destructive command (reset --hard,
force push, clean -f) as the first option without warning me first and offering the safe
alternative.