agentleFS
Sign inStart free
rodri-oliveira-devrodri-oliveira-dev/complexity-analyzers/.agents/skills/roslyn-analyzer-development/SKILL.md

roslyn-analyzer-development

Skill4 starsChanged 3 months agoMITView on GitHub

Use esta skill para implementar ou revisar codigo do Roslyn Analyzer de complexidade, incluindo diagnostics, analise sintatica, analise semantica, performance, determinismo, empacotamento e isolamento do projeto original.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use context.EnableConcurrentExecution() quando o analyzer for thread-safe.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Roslyn Analyzer Development

Objetivo

Guiar o desenvolvimento do ComplexityAnalysis.Analyzers como analyzer independente, performatico, deterministico e seguro para consumo via NuGet.

Regras obrigatorias

  • O analyzer target e netstandard2.0.
  • O analyzer nao depende dos projetos originais.
  • Nao criar ProjectReference para ComplexityAnalysis.Core, ComplexityAnalysis.Roslyn, ComplexityAnalysis.Solver, ComplexityAnalysis.Engine, ComplexityAnalysis.Calibration ou ComplexityAnalysis.IDE.
  • Nao fazer chamadas de rede.
  • Nao fazer I/O em hot paths.
  • Nao depender de banco, containers, filas, cloud ou infraestrutura.
  • Evitar estado estatico mutavel.
  • Respeitar CancellationToken.
  • Habilitar analise concorrente quando seguro.
  • Tratar generated code explicitamente.
  • Evitar Microsoft.CodeAnalysis.Workspaces enquanto nao houver CodeFix ou necessidade comprovada.
  • Usar apenas APIs necessarias de Microsoft.CodeAnalysis.
  • Performance do analyzer e requisito funcional.
  • A analise deve ser deterministica.
  • Resultados inconclusivos devem ser explicitamente representados.
  • Preferir nao reportar diagnostico a produzir falso positivo de alta severidade.
  • Qualquer logica portada do projeto original deve ter testes de caracterizacao.

Processo

  1. Leia analyzer/AGENTS.md, o projeto alvo e os testes relacionados.
  2. Confirme que a mudanca pertence ao workspace analyzer/.
  3. Para diagnostics, defina ID, categoria, severidade, mensagem, localizacao e comportamento negativo antes de implementar.
  4. Registre acoes Roslyn no nivel mais especifico suficiente.
  5. Evite trabalho repetido por node quando puder compartilhar dados imutaveis e seguros.
  6. Use context.EnableConcurrentExecution() quando o analyzer for thread-safe.
  7. Defina politica de generated code com ConfigureGeneratedCodeAnalysis.
  8. Passe CancellationToken para APIs Roslyn que o aceitam.
  9. Evite alocacoes desnecessarias em callbacks muito frequentes.
  10. Prefira estruturas imutaveis ou locais a caches globais.
  11. Teste caminhos positivos, negativos, inconclusivos e edge cases.

Validacao

dotnet restore ./ComplexityAnalysis.Analyzers.sln
dotnet build ./ComplexityAnalysis.Analyzers.sln --configuration Release --no-restore
dotnet test ./ComplexityAnalysis.Analyzers.sln --configuration Release --no-build

Para mudancas de empacotamento, valide tambem:

dotnet pack ./src/ComplexityAnalysis.Analyzers/ComplexityAnalysis.Analyzers.csproj --configuration Release --no-build -p:PackageVersion=0.0.0-local

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free