URGENT Help! Lost commits after failed rebase - how to recover?

[gemadhavi]

I messed up badly and need ugrent help recovering my work.

Background:

Working on a feature branch for the past 2 days. Made good progress - around 500 lines of code across multiple commits. Didn't push yet because I wanted to clean up the commit history first.

What Happened:

1. Was on feature/user-auth branch with 3-4 commits
2. Needed to sync with main, so did git checkout main && git pull
3. Went back and started rebasing: git rebase main
4. Hit conflicts, resolved them, git rebase --continue
5. Hit MORE conflicts (unexpected), got confused
6. Think I did git rebase --abort but not sure if it worked
7. Tried to reset to before the rebase: git reset --hard HEAD~3
8. Realized that was wrong, now my commits are gone
9. Looked at git reflog, tried resetting to what I thought was the right commit
10. Made it worse - now on detached HEAD

Current Situation:

$ git status
HEAD detached at 7f3a891
nothing to commit, working tree clean

My git reflog has like 60+ lines and I honestly can't figure out which commit has my actual work. I've tried git reset --hard to a few different commits but keep ending up in the wrong place.

What I've Tried:
git reflog - too many entries, can't identify the right one
git show on several commits - diffs are huge, hard to verify
git log --all --oneline - doesn't show my lost commits
Googling "recover lost commits git" - everyone says use reflog but I AM and it's not helping
Questions:
How do I systematically find the right commit in reflog?
Is there a way to see what each reflog entry actually contains without manually checking diffs?
Should I be looking for specific reflog messages like "rebase (start)" or "commit:"?
Is my work actually recoverable or could it be garbage collected already?

I've been stuck on this for over an hour. The reflog output is just overwhelming and I'm worried about making it worse. Any advice would be really appreciated.