Convention
Defining and sticking with a style guide helps reduce the amount of decisions that developers need to make when writing code, helping to keep their focus on logic, not semantics and formatting.
Hound comments on style violations in GitHub pull requests, allowing you and your team to better review and maintain a clean codebase.
CoffeeScript
Elixir
Go
Haml
JavaScript
Python
Ruby
Sass
Swift
TypeScript
Convention
Defining and sticking with a style guide helps reduce the amount of decisions that developers need to make when writing code, helping to keep their focus on logic, not semantics and formatting.
Consistency
When every line of code is written in the same style, the whole codebase becomes easier to read, understand and de-bug. It also helps prevent areas of the codebase from being “owned” by one person's unique style vs. the team.
Awesomeness
A clean codebase is a reflection of a cohesive team. It gives the impression of a team working well together towards a common goal, rather than individual developers working independently.
Hound integrates with your existing workflow by reviewing and commenting on code the moment a GitHub pull request is opened or updated.
Automated style checking with Hound gives developers more time to give the kind of code review that humans are best at giving.
Hound's default style guides build upon accepted industry standards and are the result of years of utilization in software projects at thoughtbot. Have your own style guide or need to modify the default? Hound provides the ability to customize your guides to best suit your team's needs.
Don’t worry, we get it. Our mission is to help you maintain a clean code base, nothing more. Our security documentation details what kind of access we need and why.