Agree. git is a bit of a pain. But, on the command line, basic solo usage is really just using a half dozen or so commands which you can easily write some shortcut aliases or functions for. As a command line tool, it’s easy to copy and paste useful tidbits for later reuse. Read up a bit on the core concepts so you’re not totally clueless about what’s going on, but leave the deep arcana commands to power users who get off talking about them.
(That’s where I am at and it serves me well)
More complicated stuff you can look up when needed, somebody will have asked about it. The nice thing is that for the most part, even if you goof up, git has probably preserved the pre-goof state somewhere.
Also, don’t be shy to just dump stuff (git archive, git show?) out into the file system and use diff tools and the like to get your bearings or merge some particularly gnarly bits, old skool. You could jot down your starting commit hash/branch when you git checkout some old stuff, that can help you find your way back.
p.s. I’d be doubly cautious asking LLMs for advice. If there’s any subject I can see hallucinations happening with, it’s gotta be them dreaming up git commands and options. If you gotta ask, verify.