Overview
Git NuGet Release Notes focuses on the package-level history that NuGet consumers actually read. Instead of updating a single repository changelog, it maps git history onto the cumulative PackageReleaseNotes.txt files that live under .nuget/{ProjectName}/ and need to stay newest-first over time.
The skill is useful in repositories where multiple packages move at different cadences or where a package ships as part of a larger family and still needs a clear, package-specific change story.
Concepts
- Per-package release history: the target is the package note file, not the repository changelog.
- Cumulative output: each update must preserve prior entries while inserting the new release at the top.
- Availability-aware summaries: the skill resolves concrete package names and versions so notes stay aligned with what can actually ship.
- Git history as source material: commit ranges and diffs inform the release story, but the final output is curated prose.
Usage guidance
Use this skill when a package is about to publish and the .nuget metadata needs to explain the release at the package boundary. It is especially helpful in monorepos or library families where repo-level notes are too broad for a package consumer.
Point it at a version or release range when you have one. Otherwise let it inspect the current branch and package layout, then produce cumulative release-note content that stays suitable for NuGet metadata.