SkillsAdd

dotnet/core · Archived

release-notes

Generate and maintain .NET release notes from `features.json`.

First seen Apr 28, 2026

Installation

$ npx skills add dotnet/core --skill release-notes
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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` to generate API diff reports and `api-diff-validation` for API verification, and a multi-model `review-release-notes` pass for final editorial QA.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

update-release-graph Same source
dotnet/core

Update the HAL+JSON release information graph when new .NET releases ship. Regenerates index fi…

3 installs
verify-releases Same source
dotnet/core

Validate releases and release links: URL liveness, file hashes, CDN latest.version files, and a…

3 installs
update-supported-os Same source
dotnet/core

Audit and update supported-os.json/md files to reflect current OS version support. Uses the rel…

3 installs
update-os-packages Same source
dotnet/core

Audit and update os-packages.json/md files that document required Linux packages for each .NET …

3 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs
azure-validate Same topic
microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…

567.7K installs
azure-aigateway Same topic
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Same topic
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Same topic
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs

Also in this package

Other skills from dotnet/core · top by installs.

npx skills add dotnet/core
update-release-graph 3 verify-releases 3 update-supported-os 3 update-os-packages 3 update-existing-branch 3 update-distro-packages 3 review-release-notes 3 publish-release-announcements 3 generate-features 3 generate-changes 3

Browse all from dotnet/core

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 22.0K
License LICENSE.TXT
Default branch main
Open issues 342
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

CompatibilityRequires GitHub MCP server or gh CLI for cross-repo queries. Pairs with the generate-changes, generate-features, update-existing-branch, editorial-scoring, api-diff, api-diff-validation, and review-release-notes skills. Claude Opus 4.6 is the default workflow model; the preferred final reviewer pair is Claude Opus 4.6 + GPT-5.4 for broader editorial feedback.
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,233 B
  • docs SUMMARY.md 458 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 4 installs

SKILL.md

.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-validation / 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](references/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.

Existing-branch reruns

When the milestone branch set already exists and contains drafted markdown, invoke [update-existing-branch](../update-existing-branch/SKILL.md). 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.

Reference documents

  • [quality-bar.md](references/quality-bar.md) — what good release notes look like
  • [vmr-structure.md](references/vmr-structure.md) — VMR branches, tags, source-manifest.json
  • [pr-layout.md](references/pr-layout.md) — base + per-component branch layout
  • [../update-existing-branch/SKILL.md](../update-existing-branch/SKILL.md) — how to refresh a populated milestone branch set incrementally
  • [changes-schema.md](references/changes-schema.md) — the shared changes.json / features.json schema
  • [../editorial-scoring/SKILL.md](../editorial-scoring/SKILL.md) — the reusable scoring rubric and cut guidance
  • [feature-scoring.md](references/feature-scoring.md) — how to score and cut features
  • [component-mapping.md](references/component-mapping.md) — components, product slugs, output files
  • [format-template.md](references/format-template.md) — markdown document structure
  • [editorial-rules.md](references/editorial-rules.md) — tone, attribution, naming
  • [api-verification.md](references/api-verification.md) — using dotnet-inspect to verify APIs
  • [examples/](references/examples/) — curated examples from previous releases, organized by component. Read the examples for your component before writing. The [examples/README.md](references/examples/README.md) lists 12 editorial principles derived from what works and what doesn't in past release notes.