I feel like this requires you to already know what all the terminology means and how it translates into commit node manipulation, in which case you don't need s

I feel like this requires you to already know what all the terminology means and how it translates into commit node manipulation, in which case you don't need something like this. Ex. "cherry-pick" and "bisect" mean very specific things in git that are not obvious. In my experience I understand trees and nodes and how they relate to commits, and I understand the operation I want to carry out on them in terms of trees, I just don't know what git calls it. So I think it would be more useful if it described common desired operations in git-agnostic terms, and then gave me the git command to do that.