I would love to create PR for it, but I do not know which section to put it.

Probably Git or Source Control.

https://github.com/conventional-changelog/commitlint

For example:

https://github.com/cjoudrey/graphql-schema-linter

Hello... add a linter for "elixir-lang"
### ie:

1. Dogma
2. Credo
3. elixir_linter

pre-commit is a utility that runs before commits can be made. The use case here is to prettier to enforce markdown style. If there is interest, I'll make a PR with a .pre-commit-config.yaml, having run prettier over the README.md.

I'd suggest organizing the 'Languages.md' file by language instead of having a gigantic list of links with several links for one language like:

# PHP

Link 1
Link 2

instead of

PHP - Link 1
PHP - Link 2

Opinions?

Java Findbugs has been replaces with SpotBugs (https://spotbugs.github.io/)
Also there are two plugins for findbugs/spotbugs which are of importance:

http://fb-contrib.sourceforge.net/

https://find-sec-bugs.github.io/

So would be nice if you could change/add this.

Add an index to the Linters' section similar to the one that is currently active for the Coding Standards' section.

It will improve usability.

Rename "Table of Contents to "COntents", as per suggestion:

• has a Table of Contents section named Contents as the first section,

This will be used in #28.

There is a small grammatical error in the first sentence.

Code linters are programs that performs static analysis on your code.

should be

Code linters are programs that perform static analysis on your code.

See #28 (comment)

Integrate project with Travis CI even if it is only to validate Markdown for the project.

The linters are the same for all of them (oclint, uncrustify, cppcheck, clang-format, clang-tidy, etc.)

Thoughts?

Add descriptions to items, as per suggestions:

• only has awesome items with descriptions (Awesome lists are curations of the best, not of everything),

This will be used in #28.

Create a custom build that will grab the .md that represents the project and generates a new website. This custom build should enable us to use the gh-pages branch currently in use.

This version not support TCL. Please adding Tool common language

Add description of the project to the top of the file, as per sugestion:

• includes a succinct description of the project/theme at the top (example),
• has been checked for inconsistent formatting, spelling, and grammar:
  • Each link description starts with an uppercase character and ends with a period.
  • Drop all the A / An prefixes in the descriptions.
  • Consistent naming. For example, Node.js, not NodeJS or node.js.

This will be used for #28.

(following PR #27)

I went looking at some PR on sindresorhus/awesome and I stumbled upon this:

By submitting this pull request I confirm I've read and complied with the below requirements.

Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things.

• I have read and understood the contribution guidelines and the instructions for creating a list.
• This pull request has a descriptive title. For example, Add Name of List, not Update readme.md or Add awesome list.
• The entry in the Awesome list should include a short description about the list project/theme (not the list itself), and should be added at the bottom of the appropriate category.
• The list I added
  • has been around for at least 30 days,
  • is the result of hard work and is the best I could possibly produce,
  • is a non-generated Markdown file in a GitHub repo,
  • is not a duplicate,
  • includes a succinct description of the project/theme at the top (example),
  • includes a project logo/illustration (whenever possible) at the top right of the readme (example). (The logo should link to the project website or any relevant website. The logo should be high-DPI, so set it to maximum half the width of the original image.),
  • only has awesome items with descriptions (Awesome lists are curations of the best, not of everything),
  • contains the awesome badge on the right side of the list heading,
  • has a Table of Contents section named Contents as the first section,
  • has an appropriate license (Meaning something like CC0, NOT a code licence like MIT, BSD, Apache, etc) (If you use a license badge, it should be SVG, not PNG),
  • has contribution guidelines,
  • doesn't include a Travis badge,
  • has been checked for inconsistent formatting, spelling, and grammar:
    • Each link description starts with an uppercase character and ends with a period.
    • Drop all the A / An prefixes in the descriptions.
    • Consistent naming. For example, Node.js, not NodeJS or node.js.

In order to be listed in the awesome repo, we would need to add a little description for each items. Does this sounds good to you?

Cppcheck is a widely known and regularly maintained open-source C++ static analysis tool. I dare say it's way more famous than the tools currently listed in the C++ category.