Release Roslynator
dotnet/roslynator
A skill your agent uses when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v release, or optionally tagging cli-v.
Agent skill
Vscode Release Notes Writer
by foryourhealth111-pixel in foryourhealth111-pixel/Vibe-Skills
Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.
Install Vscode Release Notes Writer
$ npx skills add foryourhealth111-pixel/Vibe-Skills --skill vscode-release-notes-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install foryourhealth111-pixel/Vibe-Skills vscode-release-notes-writer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/bundled/skills/vscode-release-notes-writer .claude/skills/vscode-release-notes-writer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vscode-release-notes-writer" agent skill from https://github.com/foryourhealth111-pixel/Vibe-Skills/tree/main/bundled/skills/vscode-release-notes-writer into .claude/skills/vscode-release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-release-notes-writer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/foryourhealth111-pixel/Vibe-Skills/tree/main/bundled/skills/vscode-release-notes-writerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add foryourhealth111-pixel/Vibe-Skills --skill vscode-release-notes-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install foryourhealth111-pixel/Vibe-Skills vscode-release-notes-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/bundled/skills/vscode-release-notes-writer .agents/skills/vscode-release-notes-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vscode-release-notes-writer" agent skill from https://github.com/foryourhealth111-pixel/Vibe-Skills/tree/main/bundled/skills/vscode-release-notes-writer into .agents/skills/vscode-release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-release-notes-writer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add foryourhealth111-pixel/Vibe-Skills --skill vscode-release-notes-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install foryourhealth111-pixel/Vibe-Skills vscode-release-notes-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/bundled/skills/vscode-release-notes-writer .cursor/skills/vscode-release-notes-writer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vscode-release-notes-writer" agent skill from https://github.com/foryourhealth111-pixel/Vibe-Skills/tree/main/bundled/skills/vscode-release-notes-writer into .cursor/skills/vscode-release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-release-notes-writer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/foryourhealth111-pixel/Vibe-Skills.git --path bundled/skills/vscode-release-notes-writer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add foryourhealth111-pixel/Vibe-Skills --skill vscode-release-notes-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install foryourhealth111-pixel/Vibe-Skills vscode-release-notes-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/bundled/skills/vscode-release-notes-writer .gemini/skills/vscode-release-notes-writer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vscode-release-notes-writer" agent skill from https://github.com/foryourhealth111-pixel/Vibe-Skills/tree/main/bundled/skills/vscode-release-notes-writer into .gemini/skills/vscode-release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-release-notes-writer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install foryourhealth111-pixel/Vibe-Skills vscode-release-notes-writerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add foryourhealth111-pixel/Vibe-Skills --skill vscode-release-notes-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/bundled/skills/vscode-release-notes-writer .github/skills/vscode-release-notes-writer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vscode-release-notes-writer" agent skill from https://github.com/foryourhealth111-pixel/Vibe-Skills/tree/main/bundled/skills/vscode-release-notes-writer into .github/skills/vscode-release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-release-notes-writer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add foryourhealth111-pixel/Vibe-Skills --skill vscode-release-notes-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install foryourhealth111-pixel/Vibe-Skills vscode-release-notes-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/bundled/skills/vscode-release-notes-writer .opencode/skills/vscode-release-notes-writer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vscode-release-notes-writer" agent skill from https://github.com/foryourhealth111-pixel/Vibe-Skills/tree/main/bundled/skills/vscode-release-notes-writer into .opencode/skills/vscode-release-notes-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-release-notes-writer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vscode-release-notes-writer- GitHub stars
- 3.6k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 825 words
- Files
- 6
- Skills in repo
- 81
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.
- Works in 2 steps: Insiders Release Notes: These notes… → Stable Release Notes: These notes…
- Tasks that involve Changelog and release notes
- SKILL.md covers General writing guidelines for…, Insiders Release Notes and Stable Release Notes
- Calls gh
What it does
Vscode Release Notes Writer is an agent skill from foryourhealth111-pixel/Vibe-Skills. Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `examples/v1_109.md`, `template-release-note-endgame.md` and `template-release-note-insiders.md`).
It sits in Development, covering Changelog and release notes. It works with Visual Studio Code and GitHub. The repository describes itself as: Intelligent Skill routing and workflow orchestration for AI agents — +21.12 pp reward, −29.6% tokens on SkillsBench with DeepSeekV4Flash-VE. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Changelog and release notes
Example prompts
- “Use the vscode-release-notes-writer skill to guideline for writing and reviewing Insiders and Stable release notes for Visual Studio Code”
- “/vscode-release-notes-writer”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Insiders Release Notes: These notes cover the latest features and updates in the Insiders build of VS Code. They are updated frequently as…
- Stable Release Notes: These notes summarize the key features and improvements in a stable release of VS Code. They follow a more…
What it can do on your machine
Read from SKILL.md and the folder at commit ddcaa2a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vscode Release Notes Writer loads about 1.4k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 825 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from foryourhealth111-pixel/Vibe-Skills at commit ddcaa2a, republished under its Apache-2.0 licence (© foryourhealth111-pixel). 825 words, ~1,405 tokens.
Download SKILL.mdSave it as
.claude/skills/vscode-release-notes-writer/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- vscode-release-notes-writer
- description
- Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.
Visual Studio Code Release Note Writer Guidelines
This skill is designed to help you write release notes for Visual Studio Code Insiders and Stable releases. It provides structured guidelines and examples to ensure consistency and clarity in the release notes.
There are two main types of release notes you can generate using this skill:
Insiders Release Notes: These notes cover the latest features and updates in the Insiders build of VS Code. They are updated frequently as new features are added. Their format includes sections grouped by the date of the updates. The content is generated based on closed GitHub issues and PRs for a specific milestone.
Stable Release Notes: These notes summarize the key features and improvements in a stable release of VS Code. They follow a more structured format with predefined sections for different feature areas. The release is intially created using a template and then updated by the engineering team.
Your task is help generate these release notes based on the provided guidelines, examples, and templates.
General writing guidelines for release notes
Follow the guidelines in this order of priority:
Insiders Release Notes
Insiders release notes cover the latest features and updates in the Insiders build of VS Code. They are updated frequently as new features are added. Their format includes sections grouped by the date of the updates. The content is generated based on closed GitHub issues and PRs for a specific milestone.
Your task is to generate release notes for the specified VS Code Insiders release version based on GitHub issues and PRs.
Input parameters
If no release version is specified, ask the user for the release version. If no milestone name is specified, check if the milestone name is in the frontmatter, otherwise ask the user for the milestone name. If no label is specified, use the "feature-request" label by default.
DO NOT continue until you have the release version and milestone name!!
File format
Issues are grouped in H2 sections by their closed date. The TOC must be updated to reflect the new sections and issues added.
Use this template for the Insiders release notes.
The 1.109 release notes are a concrete example.
Show full SKILL.md (451 more words)Show less
Generation steps
If there is not an existing Insiders release note for the specified version, create a new release note file using the Insiders release note template and replace the placeholders.
Release notes are stored in the
/release-notesfolder with the filename formatv<version>.md, e.g.,v1_109.md.Make sure to copy the following images to the appropriate images folder (
/release-notes/images/<version with underscores>, e.g.1_110) for the release version:vscode-insiders-header.webpvscode-insiders-banner-medium.png
Get last update date from existing release notes for the specified release version. If no existing release notes, disregard last update date.
Run a subagent to fetch all closed GitHub issues in the microsoft/vscode repo for the milestone that have the specified label and closed date as of the latest update date by using the github CLI. Save the JSON in the release note document.
Use this CLI command:
gh search issues --repo microsoft/vscode --label <label name> --milestone <milestone name> --state closed "closed:>=<latest update date>" -L 100Ignore issues that are marked as duplicate or not planned.
For each issue in the JSON result, run a subagent to update the release notes and TOC with a concise technically accurate summary of the issue. Get more details from the associated PRs if needed. At the end of the summary, include a link to the GH issue which include the issue number and title (format: #12345: Issue title). Group issues under an H2 section that represents the closed date.
Stable Release Notes
Stable release notes summarize the key features and improvements in a stable release of VS Code. They follow a more structured format with predefined sections for different feature areas. The release is intially created using a template and then updated by the engineering team.
Input parameters
If no release version is specified, ask the user for the release version. If no release month and year are specified, ask the user for the release month and year. DO NOT continue until you have the release version and release month and year!!
File format
Use this template for generating the initial Stable release notes.
Generation steps
If there is not an existing release note for the specified version, create a new release note file using the Stable release note template.
Release notes are stored in the
/release-notesfolder with the filename formatv<version>.md, e.g.,v1_109.md.If there is an existing release note for the specified version, and it's an Insiders release note, replace the content with the Stable release note template content.
If there is an existing Stable release note for the specified version, perform a code review of the existing release note to ensure it adheres to the writing guidelines. Suggest improvements as needed.
© foryourhealth111-pixel, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files in bundled/skills/vscode-release-notes-writer of foryourhealth111-pixel/Vibe-Skills.
- SKILL.md
- examples/v1_109.md
- images/vscode-insiders-banner-medium.png
- images/vscode-insiders-header.webp
- template-release-note-endgame.md
- template-release-note-insiders.md
Open the folder on GitHubat commit ddcaa2a
Compare with similar skills
Vscode Release Notes Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vscode Release Notes Writer this skillforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Release Roslynatordotnet/roslynator | 3.5k | — | ~1k | Automated safety check: Pass | Custom licence | |
| Trust CI Release GatesjohannesPettersson80/trust-platform | 222 | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Releasesignageos/vscode-sops | 122 | — | ~2.2k | Automated safety check: Notes | MIT | |
| Releasequerylenshq/ef-querylens | 225 | — | ~887 | Automated safety check: Pass | MIT | |
| Releaseforcedotcom/salesforcedx-vscode | 1k | — | ~1.7k | Automated safety check: Pass | BSD-3-Clause |
Similar skills
- Official
Trust CI Release Gates
johannesPettersson80/trust-platform
Prepares and ships truST changes - changelog and version updates, CI parity, pre-push checks, the exact-SHA release-candidate guard, merge, tag and release verification.
Release
signageos/vscode-sops
Releases the vscode-sops extension end-to-end: determines the next version from the bump history, updates CHANGELOG.md and package.json/package-lock.json, builds via vscode:prepublish, publishes to…
Release
querylenshq/ef-querylens
A skill your agent uses when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub…
Release
forcedotcom/salesforcedx-vscode
Run the VS Code extension release workflow end-to-end. An agent skill from forcedotcom/salesforcedx-vscode.
Rocky Release
rocky-data/rocky
Tag-namespaced release workflow for the Rocky monorepo. An agent skill from rocky-data/rocky.
More from foryourhealth111-pixel/Vibe-Skills
All 81 skills in this repoMarket Research Reports
foryourhealth111-pixel/Vibe-Skills
Produces long consulting-style market research and industry reports covering market sizing, competitive landscape, market entry and investment theses.
Academic Venue Templates
foryourhealth111-pixel/Vibe-Skills
Supplies venue-specific LaTeX templates and formatting rules for journals, conferences and posters, and checks a manuscript against page limits and submission requirements.
Digital Brain
foryourhealth111-pixel/Vibe-Skills
This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content…
Smart File Writer
foryourhealth111-pixel/Vibe-Skills
Diagnoses why a file write failed (permissions, disk space, path length, locks, read-only mounts) before retrying, instead of repeating the same call blindly.
Automated Video Studio
foryourhealth111-pixel/Vibe-Skills
Turns footage, audio and a storyboard plan into a finished short video with FFmpeg jump-cuts, subtitle burn-in and a final polish pass.
Citation Management
foryourhealth111-pixel/Vibe-Skills
Turns DOIs, PMIDs and arXiv IDs into clean BibTeX, searches Google Scholar and PubMed, and checks and deduplicates a reference list.
Related
Works with
Categories
Questions about Vscode Release Notes Writer
What does Vscode Release Notes Writer do?
Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code. Vscode Release Notes Writer is an agent skill from foryourhealth111-pixel/Vibe-Skills. Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.
When should I use Vscode Release Notes Writer?
Vscode Release Notes Writer fits situations like: tasks that involve Changelog and release notes.
How do I install Vscode Release Notes Writer in Claude Code?
Run `npx skills add foryourhealth111-pixel/Vibe-Skills --skill vscode-release-notes-writer -a claude-code`. Or copy the skill folder (bundled/skills/vscode-release-notes-writer in foryourhealth111-pixel/Vibe-Skills) into .claude/skills/vscode-release-notes-writer in your project. Claude Code loads it when a task matches its description.
How do I install Vscode Release Notes Writer in Codex?
Run `npx skills add foryourhealth111-pixel/Vibe-Skills --skill vscode-release-notes-writer -a codex`. Or copy the skill folder (bundled/skills/vscode-release-notes-writer in foryourhealth111-pixel/Vibe-Skills) into .agents/skills/vscode-release-notes-writer in your project. Codex loads it when a task matches its description.
Can I use Vscode Release Notes Writer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add foryourhealth111-pixel/Vibe-Skills --skill vscode-release-notes-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vscode-release-notes-writer, .gemini/skills/vscode-release-notes-writer, .github/skills/vscode-release-notes-writer and .opencode/skills/vscode-release-notes-writer in your project.
What does Vscode Release Notes Writer need to run?
Going by SKILL.md and its folder, Vscode Release Notes Writer needs the command-line tools its instructions call (gh).
Does Vscode Release Notes Writer access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Vscode Release Notes Writer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vscode Release Notes Writer use?
Vscode Release Notes Writer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vscode Release Notes Writer use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vscode Release Notes Writer?
Skills that share tags, products or a category with Vscode Release Notes Writer: Release Roslynator (dotnet/roslynator, 3.5k stars), Trust CI Release Gates (johannesPettersson80/trust-platform, 222 stars), Release (signageos/vscode-sops, 122 stars) and Release (querylenshq/ef-querylens, 225 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vscode Release Notes Writer?
foryourhealth111-pixel (a GitHub user) maintains it in foryourhealth111-pixel/Vibe-Skills, which has 3,627 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on August 31, 2026.
Source: foryourhealth111-pixel/Vibe-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.