proposal: git-flick, move a commit to another branch

While working on a feature branch, I often come across and fix various minor issues (e.g. code readability). Ideally such commits should live on a separate branch to avoid obscuring feature changes.

Based on IRC conversations (#git on FreeNode), here's what I came up with (tentatively called git-flick, for lack of inspiration):

#!/usr/bin/env bash

set -e
set -x

treeish=${1:?}
target_branch=${2:?}

git checkout "$target_branch"
git cherry-pick "$treeish"
# return to original branch
git checkout @{-1}
# remove commit from original branch
# NB: rebase shortens treeish to seven characters; rebasing from commit's parent
GIT_EDITOR="grep -v ${treeish:0:7}" git rebase -p -i "${treeish}^"

(This is not extensively tested yet.)

If this is deemed of general interest, I could submit a pull request.

The issue provides a proposed Bash entry point for git-flick; start by reviewing that script and how this repository organizes Git utilities. Done means a repository-integrated command can move a selected commit to another branch without leaving it on the original branch, with behavior validated beyond the issue's currently untested example.