Skip to content

foryourhealth111-pixel/Vibe-Skills / bundled/skills/vscode-release-notes-writer

vscode-release-notes-writer

Verified

Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.

template-release-note-insiders.md

View on GitHub
---
Order:
TOCTitle: Insiders
PageTitle: "Visual Studio Code <Month> <Year> (Insiders)"
MetaDescription: Learn what is new in the Visual Studio Code <Month> <Year> Release (1.<release number>).
MetaSocialImage: 1_<release number>/release-highlights.webp
Date: <YYYY-MM-DD>
DownloadVersion: 1.<release number>.0
Milestone: <milestone name>
---
# <Month> <Year> Insiders (version 1.<release number>)

![VS Code Insiders banner](images/1_<release number>/vscode-insiders-banner-medium.png)

_Last updated: <Month day, year>_

These release notes cover the Insiders build of VS Code and continue to evolve as new features are added. To try the latest updates, [download Insiders](https://code.visualstudio.com/insiders).
To read these release notes online, go to [code.visualstudio.com/updates](https://code.visualstudio.com/updates).

You can still track our progress in the [Commit log](https://github.com/Microsoft/vscode/commits/main) and our list of [Closed issues](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+is%3Aclosed+milestone%3A%22<Month>+<Year>%22).

_These release notes were generated using GitHub Copilot and might contain inaccuracies._

Happy Coding!

---

<!-- TOC
<div class="toc-nav-layout">
  <nav id="toc-nav">
    <div>In this update</div>
    <ul>
      <li><a href="#<month>-<day>-<year>"><Month> <day>, <year></a></li>
    </ul>
  </nav>
  <div class="notes-main">
Navigation End -->

## <Month> <day>, <year>

* Feature description with link to issue. _[#issue-number](https://github.com/microsoft/vscode/issues/issue-number)_

---

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.

<a id="scroll-to-top" role="button" title="Scroll to top" aria-label="scroll to top" href="#"><span class="icon"></span></a>
<link rel="stylesheet" type="text/css" href="css/inproduct_releasenotes.css"/>
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall