dotnet/core/generate-changes
Claude Code and agent skill by dotnet/core
- community
Checking that the SKILL.md file is still in the repository.
Generate `changes.json` for a .NET release milestone by selecting the correct VMR base/head refs and running `release-notes generate changes`. Handles preview-only multi-branch targeting (`main` vs release branches vs tags) and emits the authoritative manifest of what shipped. DO NOT USE FOR: API diffs (use api-diff), API verification (use api-diff-validation), feature scoring (use generate-features), or writing markdown release notes (use release-notes).
Install
npx vskill@latest install dotnet/core/generate-changesSKILL.md
The same SKILL.md was published earlier as dotnet/core/generate-changes.
Generate changes.json
Produce the authoritative changes.json input for a preview, RC, or GA release milestone.
This is the VMR-aware data acquisition stage of the release notes pipeline:
- Determine which milestone(s) are active
- Resolve the correct
--baseand--headrefs - Run
release-notes generate changes - Write
changes.jsoninto the correctrelease-notes/folder
When to use
- A new preview, RC, or GA milestone needs fresh shipped-change data
- The user wants to know whether multiple preview milestones are active at once
- The release notes branch should be refreshed after the VMR moved forward
changes.jsonis missing, stale, or suspected to have the wrong ref selection
Preview-only branch targeting
This is the subtle part, and it mostly matters for previews.
Multiple preview milestones can be active simultaneously:
For each target milestone N:
| Milestone state | Base ref | Head ref | |
|---|---|---|---|
| Tag exists for N | Tag for N-1 | Tag for N | |
| Release branch exists for N, no tag yet | Tag for N-1 | Release branch tip | |
Only on main | Tag for N-1 | main |
Critical rule: never use main for milestone N if main has already moved to N+1.
Inputs
The user should provide as much of this as they know:
- Target release — e.g.
.NET 11 Preview 4,.NET 10 RC 2,.NET 10 GA - VMR clone path — defaults to a local clone of
dotnet/dotnet - Optionally, the exact refs if they already know them
If the user does not specify the milestone, infer it from:
release-notes/{version}/releases.jsonin this repoeng/Versions.propsonmainin the VMR- Matching preview tags and release branches in the VMR
Process
1. Determine the floor from releases.json
Find the latest shipped milestone in this repo. That tells you the lowest in-flight milestone that may need work.
2. Inspect the VMR
- Read
eng/Versions.propsonmainto determine the current prerelease iteration - List matching VMR tags for finalized milestones
- List matching VMR release branches for stabilizing milestones
Use the VMR structure reference for naming conventions and branch patterns.
3. Resolve --base and --head
For each active milestone:
--baseis the previous shipped milestone tag--headis the milestone tag, release branch tip, ormain, depending on what exists
4. Generate the file
Examples:
Output contract
The output file must follow the shared schema documented in changes-schema.md:
- top-level
release_version,release_date,changes,commits - stable
idvalues inrepo@shortcommitformat - same authoritative source of truth used by later skills
Milestone cross-check
changes.json is derived from a VMR source-manifest diff. That makes it authoritative for what flowed into the build, but it is a commit-shaped view, and a feature can be easy to overlook in it. For the repos that maintain preview milestones, sweep the milestone as a second, independent view of the same release and reconcile anything that looks like a user-facing feature but never made it into the notes.
Milestone discipline varies by repo, so this check only applies for the repos where it is actually maintained:
- dotnet/sdk
- dotnet/aspnetcore
- dotnet/runtime
- dotnet/efcore
Rules for using it:
- Supplement, never replace.
changes.jsonstays the source of truth. The milestone is a
prompt to go back and look, not an alternative manifest.
- The milestone is a subset. It excludes infrastructure and dependency-flow PRs that
legitimately appear in changes.json, so the counts will not match and are not meant to.
- Only the missing direction matters. What is worth acting on is a PR in the milestone that
describes a user-facing change and has no corresponding entry in the notes.
- Verify every addition independently before writing it up. Milestones are applied by
automation, so they are usually right — but they can be changed or applied incorrectly by hand afterwards, and a milestoned PR can still be reverted. Treat a milestone as reliable evidence of where to look and strong but not conclusive evidence that the change shipped. Before promoting anything found this way, confirm it appears in changes.json and exists in the build (see `api-verification.md` and `validate-code-samples`). The expected outcome is that it checks out; the point is to catch the occasional one that does not.
- Confirm the milestone exists before relying on its absence. Repos without
11.xmilestones
will return zero results, which means "not tracked here", not "nothing shipped".
Once changes.json exists, the next step is usually generate-features.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryChecking.github/skills/generate-changes/SKILL.md
Popularity
- Repository stars
- 22,038
- Repository forks
- 4,939
- 7-day trend score
- 50
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 24 Sep 2026, a month ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/dotnet/core/generate-changes)