Description
Is your feature request related to a problem? Please describe.
Just curious - given the deprecation of enable-all (e.g., #542 (comment)), is there any way to find out what linters are newly available, shy of comparing the list of enabled ones to the full list on the site?
It would be extremely useful if there were an option to print available (but not enabled) linters. Also, it's great that golangci-lint supports a lot of different types of linters, but sometimes it could be more clear which ones are recommended for typical use cases, so some kind of opinionated preset would also be nice.
IMO, the recommendation it seems is being made (to explicitly list all linters by name one by one in each project's config) is a bit of a hassle / maintenance headache.
Describe the solution you'd like
A couple options - one would be a command line flag to print all available, but not enabled linters based on the current version of the tool and the current project's config.
Optionally, some other way to restore the previous behavior of allowing one to move to a more "disable explicit" mode and / or some kind of "recommended" config that would continue to add the most useful of new linters automagically.
Describe alternatives you've considered
Some kind of way to define an org-wide preset (similar to tools like, say, eslint for node) might be interesting.
Additional context
Add any other context or screenshots about the feature request here.