.NET Release Notes

Generate and maintain release notes for .NET preview, RC, and GA releases.

This skill is the editorial writing stage of the pipeline. It turns a scored features.json file into the markdown that ships in this repository.

How it works

1. generate-changes diffs source-manifest.json between VMR refs to produce changes.json
2. generate-features reads changes.json, resolves revert/backout relationships, and emits features.json with optional scores using the shared editorial-scoring rubric
3. update-existing-branch handles incremental reruns when a milestone branch already exists, merging deltas instead of restarting from scratch
4. api-diff / dotnet-inspect verifies public APIs and confirms suspect features still exist in the shipped build
5. release-notes writes curated markdown using the higher-value entries from features.json
6. review-release-notes runs a final multi-model editorial QA pass against the scoring rubric and examples
7. Output is a set of pull requests per release milestone in dotnet/core: a base PR that holds shared metadata (changes.json, features.json, README.md, build-metadata.json) and one PR per component file. Each component PR targets the base branch so component teams review and edit their file in isolation. See pr-layout.md for the full layout and naming scheme.

Local testing (no PRs)

To dry-run the skill against a milestone, only create the branch set locally. Don't push the branches or create the PRs.