Solo workflow is as simple as write code, git commit, repeat. Throw in a git push every once in a while. All on master, no branching or forking.

I do a lot of that in my solo project. I would add to your list "write a commit comment". It's like keeping a journal you can go back to. It gives me time to stop and think what have I done, what needs to be done next.

I don't much read my git-commit-comments but I think it is useful to write them.

I don't usually branch, at least at this stage of the project. Probably yes when I go to production when there is a need to fix bugs in the released version(s) without having to put all the latest code into it.

Even without branching commits are a good way to save the latest known good state I can easily go back to if things didn't work out.

That's a lot of commandline I don't normally have to bother with. And if I'm not living in the commandline then I only end up running git when I reach some milestone I want to back up... which I can do just as easily with 7zip without installing anything I don't already have, and I can copy archives to my NAS without having to set up some remote repo.

You can try and convince me until you're blue in the face dude, but I've tried it and I just don't like it. End of story.

You don't have to use the command line, most code editors have built in UI for this, especially when you're only using these basic git features.

I just use Notepad++. I like to keep my development environment simple.