Official agent skill

Prepare Release

by microsoft in microsoft/FeatureManagement-Dotnet

Prepare a release for the Feature Management .NET SDK. An agent skill from microsoft/FeatureManagement-Dotnet.

OfficialMITAuto-check passed

Install Prepare Release

skills CLI

$ npx skills add microsoft/FeatureManagement-Dotnet --skill prepare-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install microsoft/FeatureManagement-Dotnet prepare-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/microsoft/FeatureManagement-Dotnet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/prepare-release .claude/skills/prepare-release && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "prepare-release" agent skill from https://github.com/microsoft/FeatureManagement-Dotnet/tree/main/.github/skills/prepare-release into .claude/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", 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

$skill-installer install https://github.com/microsoft/FeatureManagement-Dotnet/tree/main/.github/skills/prepare-release

Type 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.

skills CLI

$ npx skills add microsoft/FeatureManagement-Dotnet --skill prepare-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install microsoft/FeatureManagement-Dotnet prepare-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/FeatureManagement-Dotnet.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/prepare-release .agents/skills/prepare-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "prepare-release" agent skill from https://github.com/microsoft/FeatureManagement-Dotnet/tree/main/.github/skills/prepare-release into .agents/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", 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.

skills CLI

$ npx skills add microsoft/FeatureManagement-Dotnet --skill prepare-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install microsoft/FeatureManagement-Dotnet prepare-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/FeatureManagement-Dotnet.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/prepare-release .cursor/skills/prepare-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "prepare-release" agent skill from https://github.com/microsoft/FeatureManagement-Dotnet/tree/main/.github/skills/prepare-release into .cursor/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", 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

$ gemini skills install https://github.com/microsoft/FeatureManagement-Dotnet.git --path .github/skills/prepare-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add microsoft/FeatureManagement-Dotnet --skill prepare-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install microsoft/FeatureManagement-Dotnet prepare-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/FeatureManagement-Dotnet.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/prepare-release .gemini/skills/prepare-release && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "prepare-release" agent skill from https://github.com/microsoft/FeatureManagement-Dotnet/tree/main/.github/skills/prepare-release into .gemini/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", 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.

GitHub CLI

$ gh skill install microsoft/FeatureManagement-Dotnet prepare-release

Installs 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).

skills CLI

$ npx skills add microsoft/FeatureManagement-Dotnet --skill prepare-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/FeatureManagement-Dotnet.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/prepare-release .github/skills/prepare-release && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "prepare-release" agent skill from https://github.com/microsoft/FeatureManagement-Dotnet/tree/main/.github/skills/prepare-release into .github/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", 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.

skills CLI

$ npx skills add microsoft/FeatureManagement-Dotnet --skill prepare-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install microsoft/FeatureManagement-Dotnet prepare-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/FeatureManagement-Dotnet.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/prepare-release .opencode/skills/prepare-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "prepare-release" agent skill from https://github.com/microsoft/FeatureManagement-Dotnet/tree/main/.github/skills/prepare-release into .opencode/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-release", 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: prepare-release
GitHub stars: 1.2k
Token cost: ~1.3k tokens
SKILL.md length: 493 words
Files: 1
Skills in repo: 1
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Prepare a release for the Feature Management .NET SDK. An agent skill from microsoft/FeatureManagement-Dotnet.

Works in 4 steps: Version Bump PR → Merge Main to Release Branch → Version Bump PR → …
User mentions release preparation
SKILL.md covers When to Use This Skill, Background, Quick Start and Review Checklist
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Prepare Release is an agent skill from microsoft/FeatureManagement-Dotnet, published by the product's own GitHub organization. Prepare a release for the Feature Management .NET SDK. Use when user mentions release preparation, version bump, creating merge PRs, preview release, or stable release for this project.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with .NET and ASP.NET Core. The repository describes itself as: Microsoft.FeatureManagement provides standardized APIs for enabling feature flags within applications. Utilize this library to secure a consistent experience when developing… The licence is MIT.

When your agent uses it

User mentions release preparation
Creating merge PRs
Preview release
Stable release for this project

Example prompts

“/prepare-release”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Version Bump PR
Merge Main to Release Branch
Version Bump PR
Merge Preview to Release Branch

What it can do on your machine

Read from SKILL.md and the folder at commit 3840350. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are powershell and xml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Prepare Release loads about 1.3k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 493 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~50
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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 microsoft/FeatureManagement-Dotnet at commit 3840350, republished under its MIT licence (© microsoft). 493 words, ~1,322 tokens.

Download SKILL.mdSave it as .claude/skills/prepare-release/SKILL.md (or your agent's skills folder).

name: prepare-release
description: Prepare a release for the Feature Management .NET SDK. Use when user mentions release preparation, version bump, creating merge PRs, preview release, or stable release for this project.

Prepare Release

This skill automates the release preparation workflow for the Feature Management .NET SDK project.

When to Use This Skill

Use this skill when you need to:

Bump the package version for a new stable or preview release
Create merge PRs to sync branches (main → release, preview → release)
Prepare all the PRs needed before publishing a new release

Background

Repository Information

GitHub Repo: https://github.com/microsoft/FeatureManagement-Dotnet
Packages (all 3 are released together with the same version):
1. Microsoft.FeatureManagement — Base package
2. Microsoft.FeatureManagement.AspNetCore — ASP.NET Core package
3. Microsoft.FeatureManagement.Telemetry.ApplicationInsights — Application Insights telemetry package

Branch Structure

main – primary development branch for stable releases
preview – development branch for preview releases
release/v{major} – release branch (e.g., release/v4)

Version Files

The version is defined by <MajorVersion>, <MinorVersion>, <PatchVersion>, and optionally <PreviewVersion> properties in all three .csproj files simultaneously:

src/Microsoft.FeatureManagement/Microsoft.FeatureManagement.csproj
src/Microsoft.FeatureManagement.AspNetCore/Microsoft.FeatureManagement.AspNetCore.csproj
src/Microsoft.FeatureManagement.Telemetry.ApplicationInsights/Microsoft.FeatureManagement.Telemetry.ApplicationInsights.csproj

Each file contains a version block like:

xml

<!-- Official Version -->
<PropertyGroup>
  <MajorVersion>4</MajorVersion>
  <MinorVersion>1</MinorVersion>
  <PatchVersion>0</PatchVersion>
</PropertyGroup>

For preview versions, a <PreviewVersion> line is also present:

xml

<!-- Official Version -->
<PropertyGroup>
  <MajorVersion>4</MajorVersion>
  <MinorVersion>0</MinorVersion>
  <PatchVersion>0</PatchVersion>
  <PreviewVersion>-preview5</PreviewVersion>
</PropertyGroup>

Version Format

Stable: {major}.{minor}.{patch} (e.g., 4.1.0)
Preview: {major}.{minor}.{patch}-preview{N} (e.g., 4.0.0-preview5)

Quick Start

Ask the user whether this is a stable or preview release, and what the new version number should be. Then follow the appropriate workflow below.

Workflow A: Stable Release

Step 1: Version Bump PR

Create a version bump PR targeting main by running the version bump script:

powershell

.\scripts\version-bump.ps1 <new_version>

For example: .\scripts\version-bump.ps1 4.2.0

The script will automatically:

Read the current version from the first .csproj file.
Create a new branch from main named <username>/version-bump-<new_version> (e.g., linglingye/version-bump-4.2.0).
Update <MajorVersion>, <MinorVersion>, <PatchVersion> in all three .csproj files, and remove <PreviewVersion> if present.
Commit, push, and create a PR to main with title: Version bump <new_version>.

When the script prompts Proceed? [y/N], confirm by entering y.

Sample PR: https://github.com/microsoft/FeatureManagement-Dotnet/pull/540

Show full SKILL.md (211 more words)Show less

Step 2: Merge Main to Release Branch

After the version bump PR is merged, create a PR to merge main into the release branch by running:

powershell

.\scripts\merge-to-release.ps1 <new_version>

For example: .\scripts\merge-to-release.ps1 4.2.0

When the script prompts Proceed? [y/N], confirm by entering y.

Important: Use "Create a merge commit" (not "Squash and merge") when merging this PR to preserve commit history.

Sample PR: https://github.com/microsoft/FeatureManagement-Dotnet/pull/541

Workflow B: Preview Release

Step 1: Version Bump PR

Create a version bump PR targeting preview by running the version bump script with the -Preview flag:

powershell

.\scripts\version-bump.ps1 <new_version> -Preview

For example: .\scripts\version-bump.ps1 4.0.0-preview4 -Preview

When the script prompts Proceed? [y/N], confirm by entering y.

Sample PR: https://github.com/microsoft/FeatureManagement-Dotnet/pull/476

Step 2: Merge Preview to Release Branch

After the version bump PR is merged, create a PR to merge preview into the release branch by running:

powershell

.\scripts\merge-to-release.ps1 <new_version> -Preview

For example: .\scripts\merge-to-release.ps1 4.0.0-preview4 -Preview

When the script prompts Proceed? [y/N], confirm by entering y.

Important: Use "Create a merge commit" (not "Squash and merge") when merging this PR to preserve commit history.

Sample PR: https://github.com/microsoft/FeatureManagement-Dotnet/pull/477

Review Checklist

Each PR should be reviewed with the following checks:

Version is updated consistently across all 3 .csproj files
No unintended file changes are included
Merge PRs use merge commit strategy (not squash)
Branch names follow the naming conventions
All CI checks pass

Files

Just SKILL.md in .github/skills/prepare-release of microsoft/FeatureManagement-Dotnet.

Open the folder on GitHubat commit 3840350

Compare with similar skills

Prepare Release 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.

Prepare Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Prepare Release this skillmicrosoft/FeatureManagement-Dotnet	1.2k	—	~1.3k	Automated safety check: Pass	MIT	yesterday
Aspnet Corefanslead/ReverseProxy.Store	163	2 repos	~1.4k	Automated safety check: Pass	Apache-2.0	1 mo ago
Aspire Integration TestingDevBetterCom/DevBetterWeb	157	2 repos	~2.3k	Automated safety check: Pass	None	4 days ago
Tsp Csharpquerylenshq/ef-querylens	225	—	~1.3k	Automated safety check: Pass	MIT	1 mo ago
Verify Authendpointsmadeyoga/AuthEndpoints	121	—	~2.6k	Automated safety check: Pass	MIT	3 days ago
Migrate Dotnet8 To Dotnet9dotnet/skills	5.6k	2 repos	~3.9k	Automated safety check: Pass	MIT	today

Similar skills

Aspnet Core
fanslead/ReverseProxy.Store
Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development.
163 GitHub starsUsed in 2 repos~1.4k tokens
Backend & APIsAuto-check passed
Aspire Integration Testing
DevBetterCom/DevBetterWeb
Write integration tests using .NET Aspire's testing facilities with xUnit.
157 GitHub starsUsed in 2 repos~2.3k tokens
Testing & QAAuto-check passed
Tsp Csharp
querylenshq/ef-querylens
Comprehensive C and .NET development skill for TSP projects.
225 GitHub stars~1.3k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed
Verify Authendpoints
madeyoga/AuthEndpoints
Drive the AuthEndpoints HTTP API via the in-repo test host (cookie sessions, Identity bearer, Simple JWT, CSRF, ReAuth).
121 GitHub stars~2.6k tokensUpdated 3 days ago
Backend & APIsAuto-check passed
Migrate Dotnet8 To Dotnet9
dotnet/skills
Official
Migrate a .NET 8 project to .NET 9 and resolve all breaking changes.
5.6k GitHub starsUsed in 2 repos~3.9k tokens
DevelopmentAuto-check passed
Migrate Dotnet9 To Dotnet10
dotnet/skills
Official
Migrate a .NET 9 project or solution to .NET 10 and resolve all breaking changes.
5.6k GitHub starsUsed in 2 repos~4.8k tokens
DevOps & CloudAuto-check passed

Works with

Questions about Prepare Release

What does Prepare Release do?

Prepare a release for the Feature Management .NET SDK. An agent skill from microsoft/FeatureManagement-Dotnet. Prepare Release is an agent skill from microsoft/FeatureManagement-Dotnet, published by the product's own GitHub organization.NET SDK.

When should I use Prepare Release?

Prepare Release fits situations like: user mentions release preparation; creating merge PRs; preview release; stable release for this project.

How do I install Prepare Release in Claude Code?

Run `npx skills add microsoft/FeatureManagement-Dotnet --skill prepare-release -a claude-code`. Or copy the skill folder (.github/skills/prepare-release in microsoft/FeatureManagement-Dotnet) into .claude/skills/prepare-release in your project. Claude Code loads it when a task matches its description.

How do I install Prepare Release in Codex?

Run `npx skills add microsoft/FeatureManagement-Dotnet --skill prepare-release -a codex`. Or copy the skill folder (.github/skills/prepare-release in microsoft/FeatureManagement-Dotnet) into .agents/skills/prepare-release in your project. Codex loads it when a task matches its description.

Can I use Prepare Release 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 microsoft/FeatureManagement-Dotnet --skill prepare-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prepare-release, .gemini/skills/prepare-release, .github/skills/prepare-release and .opencode/skills/prepare-release in your project.

What does Prepare Release need to run?

SKILL.md names no scripts, command-line tools or credentials: Prepare Release is instructions for the agent only.

Does Prepare Release access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prepare Release 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 Prepare Release use?

Prepare Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prepare Release use?

About 1.3k tokens (SKILL.md is roughly 5.3k 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 Prepare Release?

Skills that share tags, products or a category with Prepare Release: Aspnet Core (fanslead/ReverseProxy.Store, 163 stars), Aspire Integration Testing (DevBetterCom/DevBetterWeb, 157 stars), Tsp Csharp (querylenshq/ef-querylens, 225 stars) and Verify Authendpoints (madeyoga/AuthEndpoints, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prepare Release?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/FeatureManagement-Dotnet, which has 1,181 GitHub stars. The repository was last updated on October 6, 2026.

Source: microsoft/FeatureManagement-Dotnet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Prepare Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Prepare Release

When to Use This Skill

Background

Repository Information

Branch Structure

Version Files

Version Format

Quick Start

Workflow A: Stable Release

Step 1: Version Bump PR

Step 2: Merge Main to Release Branch

Workflow B: Preview Release

Step 1: Version Bump PR

Step 2: Merge Preview to Release Branch

Review Checklist

Files

Compare with similar skills

Similar skills

Aspnet Core

Aspire Integration Testing

Tsp Csharp

Verify Authendpoints

Migrate Dotnet8 To Dotnet9

Migrate Dotnet9 To Dotnet10

Related

Questions about Prepare Release