Official agent skill

Bump Aspire Version

by microsoft in microsoft/aspire

Bumps the Aspire repository product version in eng/Versions.props using previous version-bump commits as guidance.

OfficialMITAuto-check passedDevOps & Cloud

Install Bump Aspire Version

skills CLI
$ npx skills add microsoft/aspire --skill bump-aspire-version -a claude-code

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

GitHub CLI
$ gh skill install microsoft/aspire bump-aspire-version --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/aspire.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bump-aspire-version .claude/skills/bump-aspire-version && 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/

Facts

Skill name
bump-aspire-version
GitHub stars
6.3k
Token cost
~1.1k tokens
SKILL.md length
539 words
Files
2
Skills in repo
22
Repo updated
First seen
Licence
MIT

At a glance

Bumps the Aspire repository product version in eng/Versions.props using previous version-bump commits as guidance.

  • Works in 4 steps: Establish the requested version and… → Read the working-tree status and… → Read both files and inspect previous… → …
  • Asked to bump Aspire branding
  • SKILL.md covers Inspect the target and history, Run the deterministic edit, Validate and Create the PR when requested
  • Runs C# scripts from its folder; calls git and dotnet

What it does

Bump Aspire Version is an agent skill from microsoft/aspire, published by the product's own GitHub organization. Bumps the Aspire repository product version in eng/Versions.props using previous version-bump commits as guidance. Use when asked to bump Aspire branding, advance the repository to a new major or minor version, or create a version-bump PR. Not for external dependency, SDK, or container-image updates.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

It sits in DevOps & Cloud, covering Containers and Project management. It works with GitHub. The repository describes itself as: Aspire is the tool for code-first, extensible, observable dev and deploy. The licence is MIT.

When your agent uses it

  • Asked to bump Aspire branding
  • Advance the repository to a new major
  • Create a version-bump PR

Example prompts

  • “Use the bump-aspire-version skill to bump the Aspire repository product version in eng/Versions.props using previous version-bump commits as guidance”
  • “/bump-aspire-version”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Establish the requested version and target branch. Interpret X.Y as X.Y.0.
  2. Read the working-tree status and preserve unrelated changes. Use the current
  3. Read both files and inspect previous bumps, including their complete diffs so
  4. Confirm the exact target milestone exists and is open in GitHub. If it is

What it can do on your machine

Read from SKILL.md and the folder at commit a3f44d2. 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

    Ships script files (C#), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • dotnet

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, 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

Bump Aspire Version loads about 1.1k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 539 words of instructions outside code blocks.

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

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/aspire at commit a3f44d2, republished under its MIT licence (© microsoft). 539 words, ~1,125 tokens.

Download SKILL.mdSave it as .claude/skills/bump-aspire-version/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
bump-aspire-version
description
Bumps the Aspire repository product version in eng/Versions.props using previous version-bump commits as guidance. Use when asked to bump Aspire branding, advance the repository to a new major or minor version, or create a version-bump PR. Not for external dependency, SDK, or container-image updates.

Bump the Aspire repository version

The product version is defined in the first property group of eng/Versions.props. Keep the target branch's automatic milestone assignment aligned in .github/policies/milestoneAssignment.prClosed.yml. Do not replace every occurrence of the old version throughout the repository.

Inspect the target and history

  1. Establish the requested version and target branch. Interpret X.Y as X.Y.0. Ask if the target version is missing; do not infer it from the calendar or SDK.

  2. Read the working-tree status and preserve unrelated changes. Use the current session branch and follow any app-managed branch naming requirements.

  3. Read both files and inspect previous bumps, including their complete diffs so related automation changes are not missed:

    bash
    git log -8 --oneline -G '<MajorVersion>|<MinorVersion>|<PatchVersion>|AspireDashboardImageTag' -- eng/Versions.props
    git log -5 --oneline -- .github/policies/milestoneAssignment.prClosed.yml
    git show <relevant-commit>

    Useful precedents are #19139 (be77aa36da, 13.5 to 13.6) and #20037 (1fd72c6d05, 13.6 to 14.0 with an unpublished dashboard-image workaround). Prefer the latest applicable history over copying an old diff blindly.

  4. Confirm the exact target milestone exists and is open in GitHub. If it is missing or closed, ask before creating or reopening it; do not leave the policy pointing at a milestone the bot cannot assign.

Run the deterministic edit

Use the bundled C# file-based app with the repository's .NET SDK rather than generating ad-hoc editing code. From the repository root, substitute the requested version, target branch, and confirmed open milestone:

bash
dotnet run --file .agents/skills/bump-aspire-version/BumpVersion.cs -- 17.0 --branch main --milestone 17.0

--branch is the PR's target branch, not the feature branch. --milestone is explicit because servicing milestones can differ from product versions (for example, product 13.6.1 can use milestone 13.6.x). The script does not create, reopen, or query GitHub milestones; confirm availability in the previous step.

The script updates all three version components (X.Y means X.Y.0) and exactly one matching branch's milestone rule. It validates the expected file structure before writing either file and fails on missing or ambiguous matches. It preserves formatting, line endings, unrelated rules, and all other properties. Repeating the same command makes no further changes. If the file layout changes, update the script rather than bypassing its checks.

Prerelease/stabilization settings and the dashboard-image pin remain unchanged: a product version bump neither stabilizes packages nor publishes a dashboard image. Review any version-specific comments separately. Do not change other release-branch rules, dependencies, SDKs, generated APIs, or sample versions without explicit scope. The old .github/workflows/milestone-assignment.yml was removed in #20390 in favor of the policy bot; do not recreate it.

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

Validate

Review git diff --check and the complete diff. Confirm only the intended version properties, milestone assignment, and any directly related comments changed.

Confirm the resulting version components and milestone title match the request. Run the edit command again and confirm it reports both files unchanged.

Check the diff separately to confirm prerelease settings and the dashboard-image pin were preserved. If the change extends beyond metadata, run focused validation for that behavior and follow the repository's SDK setup instructions when needed.

Create the PR when requested

Use the create-pr skill and the repository PR template. Commit only the intended files, include required commit trailers, push without force, and use the available PR creation tool when the environment requires it. Describe the old and new versions, milestone routing, unchanged prerelease status, any retained dashboard-image override, and the validation actually performed. Do not claim a full build or test run unless one was performed. Do not merge automatically.

© microsoft, MIT. 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 1 other file in .agents/skills/bump-aspire-version of microsoft/aspire.

  • SKILL.md
  • BumpVersion.cs

Open the folder on GitHubat commit a3f44d2

Compare with similar skills

Bump Aspire Version 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.

Bump Aspire Version compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bump Aspire Version this skillmicrosoft/aspire6.3k—~1.1kAutomated safety check: PassMIT
Reflexo ReleaseMyriad-Dreamin/typst.ts1.2k—~1.5kAutomated safety check: PassApache-2.0
Opentagamplifthq/opentag1.4k—~1.3kAutomated safety check: NotesMIT
1panel App Builderarch3rPro/1Panel-Appstore213—~1.3kAutomated safety check: PassMIT
Releasebmeares/Meerschaum154—~1.1kAutomated safety check: NotesApache-2.0
Releasematrixorigin/memoria608—~494Automated safety check: PassApache-2.0

Similar skills

  • Reflexo Release

    Myriad-Dreamin/typst.ts

    Guide Reflexo/typst.ts release preparation and operator handoffs.

    1.2k GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Opentag

    amplifthq/opentag

    Deploy or operate OpenTag's supported paired setup when a user needs to bootstrap the self-hosted Docker Compose Control Plane and Slack Source App, configure or pair a local ACP Runner with a…

    1.4k GitHub stars~1.3k tokensUpdated 3 days ago
    DevOps & CloudAuto-check: notes
  • 1panel App Builder

    arch3rPro/1Panel-Appstore

    A skill your agent uses when packaging Docker deployments as 1Panel local app store apps, including GitHub projects, docker-compose.yml files, docker run commands, app metadata, version directories…

    213 GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Release

    bmeares/Meerschaum

    Meerschaum release process — bump version, update changelog, stage dev→main PR, run CI, publish to PyPI, tag, GitHub release, build/push Docker images, rebuild docs on prod VPS.

    154 GitHub stars~1.1k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes
  • Release

    matrixorigin/memoria

    Cut a Memoria release. An agent skill from matrixorigin/memoria.

    608 GitHub stars~494 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Resource Designer

    microsoft/terraform-provider-fabric

    Official

    Research SDK contracts, design Terraform schema approach, and compose a GitHub issue for a new resource, data source, ephemeral resource, or enhancement to an existing resource.

    128 GitHub stars~6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

More from microsoft/aspire

All 22 skills in this repo
  • Azdo Internal

    microsoft/aspire

    Official

    A skill your agent uses when asked to trigger or inspect Aspire internal Azure DevOps builds, source-index runs, or release validation on dnceng/internal; push to the internal mirror; download build…

    6.3k GitHub stars~4.5k tokensUpdated today
    Auto-check passed
  • Backport PR

    microsoft/aspire

    Official

    Backports a merged PR to a release branch by triggering the /backport bot, waiting for the bot-created PR, and filling in the shiproom template (Customer Impact, Testing, Risk, Regression?).

    6.3k GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • CI Test Failures

    microsoft/aspire

    Official

    Guide for diagnosing GitHub Actions test failures, extracting failed tests from runs, and creating or updating failing-test issues.

    6.3k GitHub stars~4.7k tokensUpdated today
    Auto-check passed
  • Create PR

    microsoft/aspire

    Official

    Create a pull request using the repository PR template. An agent skill from microsoft/aspire.

    6.3k GitHub stars~4k tokensUpdated today
    Auto-check passed
  • Dashboard Testing

    microsoft/aspire

    Official

    Guide for writing tests for the Aspire Dashboard. An agent skill from microsoft/aspire.

    6.3k GitHub stars~4.7k tokensUpdated today
    Auto-check passed
  • Deployment E2E Testing

    microsoft/aspire

    Official

    Guide for writing Aspire deployment end-to-end tests. An agent skill from microsoft/aspire.

    6.3k GitHub stars~3.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Bump Aspire Version

What does Bump Aspire Version do?

Bumps the Aspire repository product version in eng/Versions.props using previous version-bump commits as guidance. Bump Aspire Version is an agent skill from microsoft/aspire, published by the product's own GitHub organization.props using previous version-bump commits as guidance.

When should I use Bump Aspire Version?

Bump Aspire Version fits situations like: asked to bump Aspire branding; advance the repository to a new major; create a version-bump PR.

How do I install Bump Aspire Version in Claude Code?

Run `npx skills add microsoft/aspire --skill bump-aspire-version -a claude-code`. Or copy the skill folder (.agents/skills/bump-aspire-version in microsoft/aspire) into .claude/skills/bump-aspire-version in your project. Claude Code loads it when a task matches its description.

How do I install Bump Aspire Version in Codex?

Run `npx skills add microsoft/aspire --skill bump-aspire-version -a codex`. Or copy the skill folder (.agents/skills/bump-aspire-version in microsoft/aspire) into .agents/skills/bump-aspire-version in your project. Codex loads it when a task matches its description.

Can I use Bump Aspire Version 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/aspire --skill bump-aspire-version -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bump-aspire-version, .gemini/skills/bump-aspire-version, .github/skills/bump-aspire-version and .opencode/skills/bump-aspire-version in your project.

What does Bump Aspire Version need to run?

Going by SKILL.md and its folder, Bump Aspire Version needs C# for the scripts in its folder and the command-line tools its instructions call (git and dotnet).

Does Bump Aspire Version access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Bump Aspire Version 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 Bump Aspire Version use?

Bump Aspire Version 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 Bump Aspire Version use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Bump Aspire Version?

Skills that share tags, products or a category with Bump Aspire Version: Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars), Opentag (amplifthq/opentag, 1.4k stars), 1panel App Builder (arch3rPro/1Panel-Appstore, 213 stars) and Release (bmeares/Meerschaum, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bump Aspire Version?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/aspire, which has 6,348 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 8, 2026.

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