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: 4/5

The PR is not yet safe to merge because its supported Git-ref validation mode can fail solely when the selected historical tree predates the newly extracted reference file.

Findings

1.  Historical Ref Validation Fails ▶

Fix with agent prompt

### Issue 1
scripts/validate-skill-templates.ps1:2752
When `-Ref` selects a committed tree from before `grouping-examples.md` was introduced, this unconditional lookup reports the reference file as missing. The Git visual commits validation block then fails instead of validating that historical tree.

---

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

Summary

• Supports central and project-level NuGet declarations, TFM-aware resolution, prerelease intent, and offline fixtures.
• Adds structural XML update tooling and focused regression suites.
• Refactors visual-commit grouping guidance into a bundled reference and updates its validator.
• Revises repository evaluation and concurrent-validation guidance.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    Repo[.NET repository] --> Audit[Enumerate package declarations]
    Audit --> Resolve[Resolve compatible versions]
    Resolve --> Classify[Classify automatic, approval, or unresolved]
    Classify --> Apply[Apply targeted XML updates]
    Apply --> Validate[Run deterministic validation]

Loading

_{Reviews (8) · Last reviewed commit: "✅ update validation assertions for git-v..."}

[greptile-apps]

Historical Ref Validation Fails

When -Ref selects a committed tree from before grouping-examples.md was introduced, this unconditional lookup reports the reference file as missing. The Git visual commits validation block then fails instead of validating that historical tree.

Knowledge Base Used: Skill template validation automation

Prompt To Fix With AI

This is a comment left during a code review.
Path: scripts/validate-skill-templates.ps1
Line: 2752

Comment:
**Historical Ref Validation Fails**

When `-Ref` selects a committed tree from before `grouping-examples.md` was introduced, this unconditional lookup reports the reference file as missing. The Git visual commits validation block then fails instead of validating that historical tree.

**Knowledge Base Used:** [Skill template validation automation](https://app.greptile.com/geekle/-/custom-context/knowledge-base/codebeltnet/agentic/-/docs/skill-template-validation-automation.md)

---

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