skills.rest
simple-platform
simple-platformOFFICIAL
Explore all skills by this author →
GitHub

app-versioning

Manage application versioning and deployment releases using SemVer and a CLI.

1|1|Updated Jan 4, 2026
Search Tags:#devops#release management#versioning#deployment#cli#semver
One-click install
npx skills add https://github.com/simple-platform/simple-tools --skill app-versioning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-versioning
Source: https://github.com/simple-platform/simple-tools/tree/main/tools/simple-cli/internal/scaffold/templates/agent/skills/app-versioning
Command: npx skills add https://github.com/simple-platform/simple-tools --skill app-versioning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a clear and consistent strategy for managing application versions and handling deployments across different environments, ensuring a predictable release cycle.

Core Features & Use Cases

  • Semantic Versioning (SemVer): Enforces MAJOR.MINOR.PATCH versioning with pre-release identifiers for development and staging.
  • Automated Version Bumping: The CLI assists in incrementing versions based on the target environment and deployment type (new cycle, iteration, promotion).
  • Use Case: Deploying a new feature to staging, then promoting it to production while ensuring version numbers are correctly updated and tracked.

Quick Start

Use the app-versioning skill to promote the current application version to the staging environment.

Frequently Asked Questions about app-versioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage application versioning and deployments across dev, staging, and prod?▼

Manage application versioning by enforcing Semantic Versioning (SemVer) and utilizing a CLI tool to automate version bumps. This ensures predictable release cycles and correctly tracks version numbers across development, staging, and production environments.

How does semantic versioning work for pre-release environments like staging?▼

Semantic versioning for pre-release environments enforces MAJOR.MINOR.PATCH formats with specific pre-release identifiers. The CLI automates incrementing these versions based on the target environment and deployment type, such as new cycle, iteration, or promotion.

What is the best way to automate version bumps for a new release cycle?▼

Automate version bumps for a new release cycle using the integrated CLI tool. It calculates and applies the correct MAJOR, MINOR, or PATCH increments based on your specified deployment type and target environment, ensuring strict forward-only versioning.

Do I need to sync app.scl with Git for release management?▼

Yes, release management requires synchronizing the app.scl file with Git. This adherence to a strict forward-only versioning policy guarantees that application versions and deployment releases are consistently tracked and predictable.

Can I promote a version from staging to production without manual version tracking?▼

Yes, you can promote a version from staging to production without manual tracking by using the CLI tool. It automates the version bumping process, ensuring version numbers are correctly updated and synchronized with Git during the promotion.

Related Skills

Explore More Software Engineering Skills→
k97k97
4

git-commit

Analyzes git diffs to generate standardized conventional commit messages.

Community
Intermediate
jonaseck2jonaseck2
2

oss-release

Enforce CHANGELOG.md release-note structure with a 10-block rolling window.

Community
Intermediate
mgamadeusmgamadeus
3

ddd-composer-update-version

Bump composer.json versions, commit, and create git tags for Packagist releases.

Community
Intermediate
Nhqvu2005Nhqvu2005
54

release-manager

Automate version bumps, changelog generation, and release preparation from git history.

Community
Intermediate