The one's that's I actually find more useful to me is when i do a cd /path/to/file then discover it's a file not a folder, and i want to open vim, doing a vim !! would result to

vim cd /path/to/file

instead you can use just the parameter passed to cd and pass it to vim doing this

vim !!:$

Git it self is trying to help you do things easier, it adds a comment below the hashes telling you the available commands, I usually just put an r for reword
Here's the available options

p, pick = use commit,

r, reword = use commit, but edit the commit message,

e, edit = use commit, but stop for amending,

s, squash = use commit, but meld into previous commit,

f, fixup = like "squash", but discard this commit's log message,

x, exec = run command (the rest of the line) using shell,

Also a tip, reordering commit lines would reorder them in the new history you're writing, and deleting a line would drop that commit from the new history.

When i tested the find by it self, i found that it matches few things that not all people might want to delete like swf which might be a flash developer/designer exported file, also flash's cached shared objects, and some files called swz inside ~/.adobe, no idea if those are important.
Also i think your command could be reduced to just find and rm
find -name '*.swf' -exec rm {} \;