analyzer-package-audit

Audit NuGet analyzer package nuspec and nupkg contents for transitive and bundled assets.

413|64|Updated Feb 7, 2023
One-click install
npx skills add https://github.com/christianhelle/refitter --skill analyzer-package-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzer-package-audit
Source: https://github.com/christianhelle/refitter/tree/main/.squad/skills/analyzer-package-audit
Command: npx skills add https://github.com/christianhelle/refitter --skill analyzer-package-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps auditors verify that NuGet analyzer and source-generator packages expose the correct dependency surface when packed, not just what projects reference.

Core Features & Use Cases

  • Inspect generated nuspec and nupkg contents to distinguish transitive dependencies from bundled analyzer assemblies.
  • Compare shipped README/docs with the actual packed behavior to catch inconsistencies.
  • Use case: for Refitter.SourceGenerator, ensure OasReader.dll is bundled as an analyzer asset without masking Refit transitively.

Quick Start

Review the packed outputs of your analyzer package to confirm the dependency surface.

Frequently Asked Questions about analyzer-package-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit NuGet analyzer dependencies in packed nupkg outputs?

To audit NuGet analyzer dependencies, inspect the generated nuspec and nupkg contents to distinguish transitive dependencies from bundled analyzer assemblies and verify the exposed dependency surface. This checks for hidden or bundled assets.

What is the difference between transitive and bundled assets in a NuGet source-generator package?

Bundled assets are analyzer assemblies packaged directly inside the nupkg, while transitive dependencies are external packages resolved through the dependency graph. Auditing distinguishes these to ensure dependency contracts are accurate.

How do I check if my packed README documentation matches actual analyzer package behavior?

Compare shipped README documentation with the actual packed nupkg behavior to catch inconsistencies. This identifies discrepancies between documented dependency contracts and the real transitive or bundled analyzer assets.

Does this audit work for NuGet packages that bundle source generator DLLs like OasReader.dll?

Yes, this audit applies to NuGet source-generator packaging scenarios to ensure required DLLs like OasReader.dll are bundled as analyzer assets without incorrectly masking other transitive dependencies like Refit.

How do I correlate project references with packaged artifacts to report dependency discrepancies?

Correlate project references with the inspected nuspec and nupkg contents to report discrepancies in dependency contracts. This verifies that packed outputs expose the correct dependency surface rather than just project references.