release-note-reviewer
Release Note Reviewer
Review Visual Studio Code release notes and produce a clear, actionable list of recommendations. Handles both Insiders and Stable release notes, each with its own checklist.
When to Use
- After drafting or updating a release notes file.
- Before publishing or merging release notes into the main branch.
- When asked to review, proofread, or improve release notes.
Procedure
1. Determine release note type
Read the file's YAML frontmatter and check the ProductEdition field:
ProductEdition value |
Type |
|---|---|
Insiders |
Insiders |
More from microsoft/vscode-docs
content-redirect
Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects.
4release-note-writer
Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.
4frontmatter-description
Check and optimize MetaDescription frontmatter fields in VS Code documentation. Use when auditing, adding, or improving page descriptions for SEO and discoverability. Apply this when making content changes to markdown articles.
4docs-product-alignment
Audit and update docs/copilot/ documentation to accurately reflect current VS Code AI capabilities. Use when: competitive analysis reveals gaps, product launches new features, docs use outdated framing, or keyword coverage needs strengthening for discoverability by users and AI agents. Produces a gap analysis plus targeted edits across affected files.
4