Code Review from the Command Line (2018)

I’ve written a short script that shows me a visualization of how frequently the files involved in this branch change over time:

Those two commands ( and ) are how I kick off my code review: getting a birds-eye view of the change and some historical context for what I’m dealing with. For example, to review all files relative to :

At this point, you might think that all we’ve done is re-create the GitHub code review experience in Vim. By switching our code review to the terminal, we can now edit files, jump to other files, and run arbitrary commands at no cost.

Source: blog.jez.io