At this point why not create an alias or function in bashrc? Then is also portable to other setups?
Worked example: Sometimes I like to fall asleep listening to an audiobook or podcast. So I open termux on my phone, and run something like:
sleep 10 && date && mpv --volume=90 --speed=1.2 $AUDIO_FILE ; date
Ctrl+R to start reverse search
Type enough to locate last command
Ctrl+X, Ctrl+E to launch command in $EDITOR
Wrap in fn() {} or alias
Save as, or append to some file, e.g. in Vim `:w >> ~/.aliases`
Ctrl-R serves a mnemonic purpose as well.. it helps you document your workflow and processes at the shell, and not hidden in some file somewhere.
None of these are that complicated that they deserve a dedicated shell script and chmod'ing, or presence in a cloneable repo, etc.
Mind: I rely on shell history all the time, and I'm noting, admiring, and planning to adopt your commenting hack, it's ingenious.
But once a particular shell hack / one-liner / function has become sufficiently useful and proven, I'll typically add it to a shell function file (~/.bash_functions, sourced from ~/.bash_profile or ~/.bashrc), or my scripts directory (typically ~/.bin/ for personal hacks, /usr/local/bin/ if it's something I'll use from multiple accounts. Also park that under git and back it up / archive it somewhere or several somewheres.
Graduating specific oneliners into functions/scripts is also a good chance to clean them up a bit, but it's a balance that's hard to strike - too many aliases and scripts, and you quickly forget they exist :-)
I do put bigger/heftier utility functions into shell scripts - its just that I, more often than not, forget where they are and have to go searching. But with Ctrl-R, the flow does not get interrupted.
Anyway, not arguing for/against either technique - they are both appropriate when needed.
They also benefit by the further mnemonic / rediscovery trigger of existing in my local ~/.bin/ or ~/.bash_functions directory and/or file(s).