Check Rubocop offenses in your working branch

git rev-parse develop | xargs git diff --name-only | grep -E '^(app|lib|spec).*\.rb' | xargs rubocop -f simple
Assumes you are in the branch you want to run the check on. Sub 'develop' for whatever branch you commonly submit PRs to.
Sample Output
== spec/support/stripe_endpoint_helpers.rb ==
C:  6: 81: Line is too long. [82/80]
C:163:114: Space inside square brackets detected.
W:231: 25: Unused block argument - value. If it's necessary, use _ or _value as an argument name to indicate that it won't be used.

37 files inspected, 3 offenses detected

2015-01-21 08:12:18

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: