agentleFS
rodri-oliveira-devrodri-oliveira-dev/complexity-analyzers/.agents/skills/nuget-release-governance/SKILL.md

nuget-release-governance

Skill4 starsChanged 3 months agoMITView on GitHub

Use esta skill para revisar ou ajustar pack, versionamento, metadados NuGet, GitHub Actions, validacao de package, release notes e publicacao segura do analyzer. Nunca use para publicar de fato sem pedido explicito.

The file

Files
SKILL.md

NuGet Release Governance

Objetivo

Orientar mudancas de release do ComplexityAnalysis.Analyzers como pacote NuGet de Roslyn Analyzer, preservando rastreabilidade, seguranca e controle explicito de publicacao.

Quando usar

  • Alterar dotnet pack, metadados de package, .nupkg ou .snupkg.
  • Revisar versionamento, release notes ou GitHub Actions de release.
  • Validar conteudo do pacote antes de publicar.
  • Avaliar supply-chain, permissoes, secrets, assinaturas, provenance ou seguranca de pipeline.

Regras obrigatorias

  • Nunca executar dotnet nuget push sem solicitacao explicita.
  • Nunca criar GitHub Release sem solicitacao explicita.
  • Nunca publicar pacote real automaticamente.
  • Nunca ampliar permissoes de workflow sem justificativa.
  • Nunca introduzir segredo em arquivo versionado.
  • O package do analyzer deve carregar o assembly em analyzers/dotnet/cs/.
  • Roslyn e ferramentas de desenvolvimento devem permanecer privadas quando aplicavel.
  • O pacote nao deve expor dependencias transitivas desnecessarias.

Checklist de package

  • PackageId, Description, tags e repository metadata estao corretos.
  • PackageVersion foi informado de forma explicita no pack.
  • .nupkg contem o DLL do analyzer em analyzers/dotnet/cs/.
  • .nupkg nao contem lib/netstandard2.0/ para o assembly do analyzer.
  • .nupkg nao contem DLLs do projeto original.
  • Roslyn nao aparece como dependencia transitiva no .nuspec.
  • .snupkg so e produzido quando configurado intencionalmente.
  • Release notes descrevem mudancas observaveis e breaking changes.

Validacao

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

Inspecione o .nupkg localmente antes de concluir alteracoes de empacotamento.

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.