Bump the SSW.VerticalSliceArchitecture.Template NuGet package version to cut a new release.

MITAuto-check passedDevelopment

Install Bump Version

skills CLI
$ npx skills add SSWConsulting/SSW.VerticalSliceArchitecture --skill bump-version -a claude-code

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

GitHub CLI
$ gh skill install SSWConsulting/SSW.VerticalSliceArchitecture bump-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/SSWConsulting/SSW.VerticalSliceArchitecture.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/bump-version .claude/skills/bump-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-version
GitHub stars
407
Token cost
~841 tokens
SKILL.md length
435 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Bump the SSW.VerticalSliceArchitecture.Template NuGet package version to cut a new release.

  • Works in 4 steps: Packs the template with nuget pack. → Pushes the .nupkg to NuGet.org. → Reads from the nuspec and creates a… → …
  • The user says bump the version
  • SKILL.md covers What "bump the version" means…, Versioning scheme: CalVer, Steps and Guardrails, plus 1 more section
  • Calls git, dotnet and gh

What it does

Bump Version is an agent skill from SSWConsulting/SSW.VerticalSliceArchitecture. Bump the SSW.VerticalSliceArchitecture.Template NuGet package version to cut a new release. Use when the user says "bump the version", "cut a release", "release a new version", "publish a new package version", or similar for this template repo. Edits the version in VerticalSliceArchitecture.nuspec — which is what triggers the publish — but never pushes or opens a PR.

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

It sits in Development. It works with .NET and Git. The repository describes itself as: An enterprise ready solution template for Vertical Slice Architecture. This template is just one way to apply the Vertical Slice Architecture. The licence is MIT.

When your agent uses it

  • The user says bump the version
  • Release a new version
  • Publish a new package version
  • Similar for this template repo

Example prompts

  • “bump the version”
  • “cut a release”
  • “release a new version”
  • “/bump-version”

Workflow steps

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

  1. Packs the template with nuget pack.
  2. Pushes the .nupkg to NuGet.org.
  3. Reads from the nuspec and creates a matching git tag.
  4. Publishes a GitHub release on that tag with auto-generated notes.

What it can do on your machine

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

    • git
    • dotnet
    • gh

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

  • Network

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

Bump Version loads about 841 tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 435 words of instructions outside code blocks.

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

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 SSWConsulting/SSW.VerticalSliceArchitecture at commit 42e7a70, republished under its MIT licence (© SSWConsulting). 435 words, ~841 tokens.

Download SKILL.mdSave it as .claude/skills/bump-version/SKILL.md (or your agent's skills folder).
name
bump-version
description
Bump the SSW.VerticalSliceArchitecture.Template NuGet package version to cut a new release. Use when the user says "bump the version", "cut a release", "release a new version", "publish a new package version", or similar for this template repo. Edits the version in VerticalSliceArchitecture.nuspec — which is what triggers the publish — but never pushes or opens a PR.
author
Daniel Mackay

What "bump the version" means in this repo

This repo is a dotnet new template published to NuGet as SSW.VerticalSliceArchitecture.Template. The release is push-triggered, not tag-triggered.

.github/workflows/package.yml runs only when a push to main changes VerticalSliceArchitecture.nuspec. When it does, it:

  1. Packs the template with nuget pack.
  2. Pushes the .nupkg to NuGet.org.
  3. Reads <version> from the nuspec and creates a matching git tag.
  4. Publishes a GitHub release on that tag with auto-generated notes.

So the <version> value in VerticalSliceArchitecture.nuspec is the release. Changing it and merging to main ships a new package. Nothing else cuts a release.

Versioning scheme: CalVer

Versions are calendar dates, YYYY.MM.DD (e.g. 2025.12.10, 2026.06.12). There is no SemVer major/minor/patch decision — the new version is simply today's date.

To find the latest published version, use gh release view --json tagName -q .tagName — that's authoritative. Don't trust git tag --sort=-v:refname | head: the repo has both v-prefixed and bare tags (v2025.10.24 and 2025.12.10), and the mixed namespace makes that sort return a stale tag above the real latest.

Steps

  1. Read the current <version> from VerticalSliceArchitecture.nuspec.
  2. Compute today's date as YYYY.MM.DD. That is the new version.
  3. Guard against a same-day re-release: run git fetch --tags first (release tags are created by CI on the remote, so a local-only git tag can miss one shipped earlier today), then check the date isn't already a tag. If it is, a release already shipped today — append a numeric suffix (YYYY.MM.DD.1) or ask the user how they want to disambiguate. Don't silently overwrite.
  4. Update <version> to the new value.
  5. Refresh <releaseNotes>: summarise what changed since the last release. The <version> you read in step 1 (before bumping) is the previous release's tag, so use it as the changelog base: git log --oneline <previous-version>..HEAD. Distil that into a short, human summary (one or two sentences). This is the NuGet page blurb — GitHub generates the full PR-list notes separately, so keep it terse.
  6. Run the humanizer skill over the release-notes prose before finishing (per the repo/global content-writing rule).
Show full SKILL.md (94 more words)Show less

Guardrails

  • Don't push. Don't open a PR. Don't merge to main. Editing the nuspec on main is what triggers the publish, so that final step is the user's call — leave the change as a reviewable diff.
  • Only touch VerticalSliceArchitecture.nuspec. The package versions in Directory.Packages.props are unrelated to the template's release version.
  • Don't edit the workflow.

Verify

The change is metadata only — no build or test impact. Re-read the nuspec diff to confirm the version and notes are right. CI runs nuget pack (which needs mono) on merge, so there's nothing useful to run locally.

© SSWConsulting, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/bump-version of SSWConsulting/SSW.VerticalSliceArchitecture.

Open the folder on GitHubat commit 42e7a70

Compare with similar skills

Bump 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 Version compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bump Version this skillSSWConsulting/SSW.VerticalSliceArchitecture407—~841Automated safety check: PassMIT
GitVersion .NET DevelopmentGitTools/GitVersion3.1k—~1.7kAutomated safety check: PassMIT
Setup Husky DotnetSebastienDegodez/copilot-instructions198—~1.3kAutomated safety check: PassApache-2.0
Git HooksProrise-cool/Claude-Code-Multi-Agent305—~3.6kAutomated safety check: NotesNone
Update Dotty Docsnewrelic/newrelic-dotnet-agent117—~2.1kAutomated safety check: PassApache-2.0
Try Fix Alternative Approachdotnet/maui23k—~8.4kAutomated safety check: PassMIT

Similar skills

  • GitVersion .NET Development

    GitTools/GitVersion

    Gives repository-specific .NET guidance for GitVersion: build and test commands, central package management, project layout and coding conventions.

    3.1k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed
  • Setup Husky Dotnet

    SebastienDegodez/copilot-instructions

    A skill your agent uses when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically

    198 GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Git Hooks

    Prorise-cool/Claude-Code-Multi-Agent

    Central authority on git hook implementations, modern best practices, and tooling for .NET/C, JavaScript/TypeScript, Python, and polyglot repositories.

    305 GitHub stars~3.6k tokensUpdated 22 days ago
    DevelopmentAuto-check: notes
  • Update Dotty Docs

    newrelic/newrelic-dotnet-agent

    A skill your agent uses when the user mentions a Dotty PR, dotty (package/dependency) updates, or asks to update the .NET agent compatibility docs / net-agent-compatibility-requirements after tested…

    117 GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Official

    Attempts one alternative fix for a bug, runs the given test command against it and reports what happened, always differing from existing PR fixes.

    23k GitHub stars~8.4k tokensUpdated today
    DevelopmentAuto-check passed
  • API Review

    microsoft/aspire

    Official

    Reviews .NET API surface area PRs for design guideline violations.

    6.3k GitHub stars~6.1k tokensUpdated today
    DevelopmentAuto-check passed

More from SSWConsulting/SSW.VerticalSliceArchitecture

  • Add Entity

    SSWConsulting/SSW.VerticalSliceArchitecture

    Scaffold a new domain entity or aggregate in this Vertical Slice Architecture template — the entity itself, its strongly typed ID, errors, specification, EF Core configuration, DbSet, the mandatory…

    407 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Add Slice

    SSWConsulting/SSW.VerticalSliceArchitecture

    Scaffold a slice in this Vertical Slice Architecture template — one use case in its own folder, with its FastEndpoints endpoint, request, response, validator, and summary, plus the Feature and Group…

    407 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Aspire

    SSWConsulting/SSW.VerticalSliceArchitecture

    A skill your agent uses when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the…

    407 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Add Adr

    SSWConsulting/SSW.VerticalSliceArchitecture

    Write an Architectural Decision Record in this repo's docs/adr/ following its Log4brains conventions — filename, title, metadata, and the sections that are required versus optional.

    407 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Bump Version

What does Bump Version do?

Bump the SSW.VerticalSliceArchitecture.Template NuGet package version to cut a new release. VerticalSliceArchitecture.Template NuGet package version to cut a new release.

When should I use Bump Version?

Bump Version fits situations like: the user says bump the version; release a new version; publish a new package version; similar for this template repo.

How do I install Bump Version in Claude Code?

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

How do I install Bump Version in Codex?

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

Can I use Bump 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 SSWConsulting/SSW.VerticalSliceArchitecture --skill bump-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-version, .gemini/skills/bump-version, .github/skills/bump-version and .opencode/skills/bump-version in your project.

What does Bump Version need to run?

Going by SKILL.md and its folder, Bump Version needs the command-line tools its instructions call (git, dotnet and gh).

Does Bump Version access the network?

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

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

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

About 841 tokens (SKILL.md is roughly 3.4k 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 Version?

Skills that share tags, products or a category with Bump Version: GitVersion .NET Development (GitTools/GitVersion, 3.1k stars), Setup Husky Dotnet (SebastienDegodez/copilot-instructions, 198 stars), Git Hooks (Prorise-cool/Claude-Code-Multi-Agent, 305 stars) and Update Dotty Docs (newrelic/newrelic-dotnet-agent, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bump Version?

SSWConsulting (a GitHub organization) maintains it in SSWConsulting/SSW.VerticalSliceArchitecture, which has 407 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

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