> I've thought about doing something similar with my shell history to help me figure out which shell aliases I should create.

Same here, I end up doing `h | grep "(something about the command)` a lot to get commands with specific options, etc. and think "damn i should really make an alias for this" every single time, but never get around to it

>figure out which shell aliases

I use shell functions for this type stuff, and I have it spit out the command line it's going to run with all the args (to stderr) and then running the command, and other sorts of programmatic touchup (tell me if i'm in the wrong directory, or whatever)

spitting out the command line it's going to run with all the args (to stderr) is a function too. shell functions can also do nice things like change the directory in my outside shell, set environment variables, etc.

ooh love it! I also have a HUGE bash aliases file, but that's all manually constructed, not automatic. some favs:

cm = git commit -m st = git status inst = sudo apt get install -y fucking = sudo