When comparing rubocop vs Code Climate, the Slant community recommends Code Climate for most people. In the question“What are the best tools for Ruby code review?” Code Climate is ranked 1st while rubocop is ranked 2nd. The most important reason people chose Code Climate is:
Code Climate gives you suggestions on how to improve the code which you can catalog on Jira.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Makes sure code fits community's style guide
Pro Gives code improvement suggestions
Code Climate gives you suggestions on how to improve the code which you can catalog on Jira.
Pro Integration with team chat software
Code Climate directly integrates with team chat tools like Slack or HipChat.
Pro Shows test code coverage
Code Climate is fully integrated with test coverage statistics and metrics, giving you a complete view and understanding of them.
Pro Free for open source
Code Climate is completely free for open source projects.
Cons
Con Mostly for web development languages
Code Climate only supports web development projects at the moment. Or at least languages that are widely used in web development (JavaScript, Ruby, Python and PHP). It has no support for largely used languages like Java or C++.
Con Repository token must be set manually for open source projects
The other services tend to automatically integrate with CI services like Travis, but Code Climate requires you to copy your repo's token into your CI service's environment.
Con Web interface doesn't show hits per line
Most code coverage services show both what lines of code were run and how many times each line was run, but Code Climate only shows the former.