Wouldn't be simpler to include some sort of configuration file? a la ".gitignore" or "packages.config"?
In this file (that travels with the sources) the team can enable/disable analyzers. Or is needed even configure them.
We can reload configuration as the file changes, again, enabling/disabling analyzers and options. This way you don't need to create custom packs.
Later on, we can try to "standardize" the configuration as other projects can use it. So, one config file for solution that potentially works with many tools, primarily with CC.

For compilation time, is it possible create a NuGet Package that install all analyzers packages, but at Editor time (VSIX). I don't know how to to this.

I just remembered that we can use the code analysis infrastructure. Instead of generating a whole new assembly, we could just generate the rule set and deliver the same assembly. Or maybe they use the default rule set editor.

The .ruleset file is an xml that looks like this:

<?xml version="1.0" encoding="utf-8"?>
<RuleSet Name="Code Cracker Rules" Description="Whatever." ToolsVersion="14.0">
  <Rules AnalyzerId="CodeCracker" RuleNamespace="CodeCracker">
    <Rule Id="CodeCracker.CatchEmptyAnalyzer" Action="None" />
    <Rule Id="CodeCracker.EmptyCatchBlockAnalyzer" Action="None" />
  </Rules>
</RuleSet>

Yes, developer can do this and configure your environment. But this work with build servers ?

I believe it will, if you commit the .ruleset file. I would have to check how the .csproj/.kroj/project.json uses it.

+1 on config file. You can still provide something like the JQuery UI download Builder to help out generating the config file, but I would definitely try to avoid generating different nuget packages for this as generating unique package ids would end up being ugly.

I just verified that the .ruleset is added to csproj:

This is what is added:

 <CodeAnalysisRuleSet>newrules.ruleset</CodeAnalysisRuleSet>

So we could maybe have a download page that prepared the nuget installation (Install-Package CodeCracker) and added the .ruleset to the project. How about that?

Cool!

We decided that this is not the time to work on this item, it is too early. We will leave it on the backlog and up for grabs. We have decided that the focus should be on analyzers and code fixes at the moment. If you want to work on this item just comment here and we will discuss with you an implementation.

@code-cracker/owners It has become really simple in Visual Studio 2015 to decide what diagnostics you want. I will close this issue because of that, if you want we can discuss it later.