feat(lint): add more linters

[jimexist]

What this PR does
add more linters

why we need it
cover more lint cases

Special notes for your reviewer:

[coveralls]

Coverage remained the same at 75.776% when pulling 6c50387 on add-linter into 16ac175 on master.

[coveralls]

Coverage remained the same at 92.34% when pulling 6f8fcb6 on add-linter into 1497682 on master.

[coveralls]

Coverage remained the same at 92.34% when pulling e435390 on add-linter into 1497682 on master.

[coveralls]

Coverage remained the same at 92.34% when pulling e435390 on add-linter into 1497682 on master.

[coveralls]

Coverage remained the same at 92.34% when pulling e435390 on add-linter into 1497682 on master.

[ddysher]

Please use our commit style

add more linters

Please remove such commits

Merge branch 'master' into add-linter

What's the criteria for adding a new linter?

[jimexist]

@ddysher can we ignore the specific commit messages, if we enforce squash commits for pull requests? So that:

• for individual comments before merging, we can revert or cherry-pick one specific pervious commit, if there is a request to change from PR comment
• we can better identify bugs introduced by merging from master if they are causing passing builds to start to fail in a PR
• upon merging, there will still be only one merge commit per PR, resulting a clean master branch (i.e. one commit per feature).

[jimexist]

criteria for adding linters:

• they make sense and are commonly supported
• until they introduced too much overhead in future development (e.g. enforcing a specific comment tag on EVERY function and struct).

[coveralls]

Coverage remained the same at 92.34% when pulling 186d391 on add-linter into 1497682 on master.

[coveralls]

Coverage remained the same at 92.34% when pulling 186d391 on add-linter into 1497682 on master.

[supereagle]

@jimexist Please fork this repo and create the PR from your forked repo.

[ddysher]

Good catch! @supereagle

@jimexist Please fork this repo and create the PR from your forked repo.

[coveralls]

Coverage remained the same at 92.34% when pulling 539d203 on add-linter into afcfe8a on master.

[ddysher]

@jimexist Since there is already conflict, can we close the PR and then create a new PR from your own fork?