RubyFlow : The Ruby Community Blog

Home   Submit   Sign Up   Log In   leaders   Twitter   RSS Feed  
 

mmozuras — 7 posts

http://codingfearlessly.com

Pronto performs quick automated code reviews with the help of various analysis tools (RuboCop, Brakeman, Flay, etc.) by checking only the introduced changes. And now it also lints your HAML with the help of HAML-Lint. Check it out: Pronto and pronto-haml.
Pronto performs quick automated code reviews with the help of various analysis tools (RuboCop, Brakeman, Flay, etc.) by checking only the introduced changes. And now it lints your chef cookbooks with the help of Food Critic. Check it out: Pronto and pronto-foodcritic.
Pronto reeks! No, wait, that's not right... Actually, Pronto performs quick automated code reviews with the help of various analysis tools (RuboCop, Brakeman, Flay, etc.) by checking only the introduced changes. And now it detects various code smells with the help of Reek. Check it out: Pronto and pronto-reek.
Pronto performs quick automated code reviews with the help of various analysis tools (RuboCop, Brakeman, Flay, etc.) by checking only the introduced changes. And now it does spell checking with the help of Aspell. Could easily be used on pull request for a blog post, for example. Check it out: Pronto and Pronto spell-checking runner.
Pronto performs quick automated code reviews with the help of various analysis tools (RuboCop, Brakeman, Flay, etc.) by checking only the introduced changes. And now it supports JavaScript with the help of jshintrb. Check it out: Pronto and Pronto runner for JSHint.
As the name suggests, Poper is partly inspired by tpope. Its purpose: to check whether your commit messages are well-formed and not generic ('oops, fix tests'). It was written to be used by Pronto, but I can easily imagine other usages also. Check it out: Poper.
Pronto runs various analysis tools (Rubocop, Flay, Brakeman...) quickly by checking only the introduced changes. That's very useful if your codebase is pretty big and/or would result in a lot of output from those tools. It's already being run on every pull request in our company!