good
Take a closer look at your git history.
The goal of good is to analyze what you've been working on. I wrote good because I'm committing to git repositories that are both public and private, and I'd like to record what I'm working on.
Good takes an email and path as arguments and tries to find all of the commits it can:
$ good --email=graham.abbott@gmail.com
+js | 104000
+py | 44554
+css | 27418
+html | 23340
+go | 5343
+txt | 3115
+md | 2950
+svg | 2006
+erl | 1507
+genie | 622
+coffee | 386
+atom | 333
+json | 308
+sql | 176
...
A commit history file is stored in your HOME directory so you can do some analysis of your own as well.
In order to install good you'll need to do the following:
go get github.com/libgit2/git2go
cd $GOPATH/src/github.com/libgit2/git2go/
git submodule update --init # get libgit2
make install
go get github.com/graham/good
If you already have git2go installed you'll only need the last line.
Then just go to directory of your choice and run good.
You can also bound the search with the --days argument:
good --email=graham.abbott@gmail.com --days=10
+go | 285
+md | 42