V0.10.0/dotnet nuget update

[gimlichael]

This pull request introduces the new dotnet-nuget-update skill, a deterministic tool for auditing and updating NuGet dependencies in .NET repositories. It ensures every declared package version is accounted for before any update, supports both central and project-level package management, preserves compatibility markers, and offers both interactive and automated update modes. The update also adds comprehensive documentation, test coverage, and offline-testable scripts.

New skill: dotnet-nuget-update

• Introduces the dotnet-nuget-update skill for complete NuGet dependency auditing and updating, supporting central and project-level versioning, TFM-band awareness, stable/prerelease intent inference, and two interactive modes (normal and yolo). [1] [2]
• Bundles deterministic scripts for dependency graph enumeration, package version resolution, TFM matrix discovery, and minimal XML edits that preserve comments and structure.
• Implements per-process memoization for NuGet feeds and supports deterministic offline testing via filesystem fixtures.
• Enforces a complete-audit invariant and preserves XML comments as update notes, requiring explicit attention for rationale-marked updates.
• Documents the skill in the README.md with catalog entry, installation instructions, and a detailed "Why dotnet-nuget-update?" section explaining its approach to dependency management. [1] [2] [3]

Release and documentation updates

• Adds a new 0.10.0 release entry in CHANGELOG.md describing the new skill and its features.
• Links the new release in the version history section.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge, with one non-blocking reporting defect in the new runner's dry-run summary.

Findings

1.  Dry Runs Count As Applied ▶

Fix with agent prompt

### Issue 1
skills/dotnet-nuget-update/scripts/Update-NuGetPackages.ps1:79
When `-DryRun` previews pending safe updates, this count includes each `dry-run` outcome in `appliedCount`, even though `Apply-PackageUpdates.ps1` does not write those changes. Callers using this field to distinguish a preview from a completed update therefore receive an inaccurate summary.

```suggestion
$successfulApplyCount = @($applyResults | Where-Object { $_.outcome -eq 'applied' }).Count
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

• Audits and applies safe package updates while preserving held notes, major updates, and unresolved rows.
• Resolves deduplicated package IDs across independent feeds with bounded concurrency and deterministic merging.
• Updates repository validation, documentation, tests, and the release catalog for the new skill.
• Re-checking confirmed that all previous Greptile threads are resolved.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    Repo[.NET repository] --> Audit[Dependency audit]
    Sources[NuGet sources] --> Resolve[Bounded parallel resolution]
    Resolve --> Audit
    Audit --> Plan[Safe update plan]
    Plan --> Apply[Structural XML apply]
    Audit --> Held[Notes, majors, unresolved]
    Apply --> Result[Update summary]
    Held --> Result

Loading

_{Reviews (9) · Last reviewed commit: "💬 update repository readme and release ..."}

[greptile-apps]

Dry Runs Count As Applied

When -DryRun previews pending safe updates, this count includes each dry-run outcome in appliedCount, even though Apply-PackageUpdates.ps1 does not write those changes. Callers using this field to distinguish a preview from a completed update therefore receive an inaccurate summary.

Suggested change

	$successfulApplyCount = @($applyResults | Where-Object { $_.outcome -in @('applied', 'dry-run') }).Count
	$successfulApplyCount = @($applyResults | Where-Object { $_.outcome -eq 'applied' }).Count

Prompt To Fix With AI

This is a comment left during a code review.
Path: skills/dotnet-nuget-update/scripts/Update-NuGetPackages.ps1
Line: 79

Comment:
**Dry Runs Count As Applied**

When `-DryRun` previews pending safe updates, this count includes each `dry-run` outcome in `appliedCount`, even though `Apply-PackageUpdates.ps1` does not write those changes. Callers using this field to distinguish a preview from a completed update therefore receive an inaccurate summary.

```suggestion
$successfulApplyCount = @($applyResults | Where-Object { $_.outcome -eq 'applied' }).Count
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.