Generate and maintain .NET release notes from `features.json`. Uses `generate-changes` for authoritative shipped-change data, `generate-features` for scoring/triage, `update-existing-branch` for incremental reruns on populated branches, `editorial-scoring` for the shared rubric, `api-diff`/`dotnet-inspect` for API verification, and a multi-model `review-release-notes` pass for final editorial QA.
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.
generate-changes diffs source-manifest.json between VMR refs to produce changes.jsongenerate-features reads changes.json, resolves revert/backout relationships, and emits features.json with optional scores using the shared editorial-scoring rubricupdate-existing-branch handles incremental reruns when a milestone branch already exists, merging deltas instead of restarting from scratchapi-diff / dotnet-inspect verifies public APIs and confirms suspect features still exist in the shipped buildrelease-notes writes curated markdown using the higher-value entries from features.jsonreview-release-notes runs a final multi-model editorial QA pass against the scoring rubric and examplesWhen the milestone branch already exists and contains drafted markdown, invoke
update-existing-branch. That shared
skill is the canonical playbook for refreshing changes.json, merging the delta
into features.json, integrating new material into existing sections, and
handling review comments without clobbering human edits.
changes.json / features.json schema