Reviews .NET documentation for a new major release that has reached general availability. Use to remove stale release-stage labels while preserving valid preview references, and to review updateeachrelease articles.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Use this skill for a yearly release-status pass when a new .NET release reaches general availability (GA). Remove stale preview or release-candidate status only where the text describes the release itself. Preserve accurate feature previews, historical examples, and general prerelease guidance.
Confirm these details before editing:
Don't assume that a request for one checklist item authorizes work on every item in the larger release checklist.
Search the repository for the release's version numbers and status terms, including Markdown articles, front matter, tables, templates, code samples, and configuration files.
Also find every article tagged with ms.custom: updateeachrelease. Review each matching article for release-specific content that this task covers. Don't skip this pass because a page wasn't found by a search for the new version number. Don't update unrelated version guidance merely because the article has this tag.
Record candidate paths and classify each occurrence before editing. A text match alone doesn't establish that a reference is stale.
Apply these rules to every candidate:
| Reference type | Action |
|---|---|
| Release-status text that says the target .NET release is in preview or RC | Update it to reflect GA, or remove it if it no longer applies |
| Feature status that remains preview after the release | Keep the preview notice unless an authoritative source confirms that the feature shipped |
| General prerelease SDK instructions or guidance that applies to future releases | Preserve it unless the task explicitly asks to change it |
| Historical or illustrative version examples | Keep them when they explain a tool or workflow; use a specific version rather than replacing it with a placeholder |
| Preview references to another release | Leave them unchanged unless the task includes that release |
| Templates or shared guidance that reviewers asked to preserve | Revert or avoid edits to those files |
For example, a GA release can still include preview features. Don't remove a feature-level preview notice just because the containing .NET or language release is GA. Conversely, don't describe the entire release as preview solely because one feature remains in preview.
ms.custom: updateeachrelease articles in the task's scope.Summarize:
updateeachrelease review performed and any in-scope changes made.dotnet/docs
affa518
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.