Setup semantic versioning with validation and templates for Python and TypeScript projects
Sets up automated semantic versioning with GitHub Actions, conventional commits, and version tracking for Python or TypeScript/JavaScript projects. Use when you need standardized versioning and release automation.
/plugin marketplace add vanman2024/dev-lifecycle-marketplace/plugin install versioning@dev-lifecycle-marketplacepython|typescript|javascriptšØ EXECUTION NOTICE FOR CLAUDE
When you invoke this command via SlashCommand, the system returns THESE INSTRUCTIONS below.
YOU are the executor. This is NOT an autonomous subprocess.
Immediately after SlashCommand returns, start executing Phase 0, then Phase 1, etc.
See @CLAUDE.md section "SlashCommand Execution - YOU Are The Executor" for detailed explanation.
CRITICAL: All generated files must follow security rules:
@docs/security/SECURITY-RULES.md
Arguments: $ARGUMENTS
Goal: Setup automated semantic versioning with GitHub Actions, conventional commits, and package publishing
Core Principles:
To use a skill: !{skill skill-name}
Actions:
Actions:
!{bash git rev-parse --git-dir 2>&1}!{bash git config user.name && git config user.email}!{bash test -f VERSION && echo "exists" || echo "not found"}!{bash mkdir -p .github/workflows}If prerequisites fail, display error and provide fix instructions.
Route to appropriate setup agent based on project type:
For Python projects:
Task(
description="Setup Python versioning",
subagent_type="versioning:python-version-setup",
prompt="Setup Python backend versioning with bump-my-version, GitHub Actions, and PyPI publishing support.
**Input Parameters**:
- project_path: current directory
- release_branches: ['main', 'master']
- github_actions: true
- pypi_publish: false (default, can be enabled via flag)
Execute all setup steps and return completion status."
)
For TypeScript/JavaScript projects:
Task(
description="Setup TypeScript/JavaScript versioning",
subagent_type="versioning:typescript-version-setup",
prompt="Setup TypeScript frontend versioning with semantic-release, GitHub Actions, and NPM publishing support.
**Input Parameters**:
- project_path: current directory
- release_branches: ['main', 'master']
- github_actions: true
- npm_publish: false (default, can be enabled via flag)
Execute all setup steps and return completion status."
)
Actions:
!{bash cat VERSION | jq .}!{bash test -f .github/workflows/version-management.yml && echo "ā Created" || echo "ā Missing"}!{bash test -f .gitmessage && echo "ā Created" || echo "ā Missing"}Actions:
Display setup completion:
ā
Semantic Versioning Setup Complete
Project Type: $PROJECT_TYPE
Current Version: <version from VERSION file>
Files Created:
- VERSION (version tracking)
- .github/workflows/version-management.yml (automated releases)
- .gitmessage (commit template)
- CONVENTIONAL_COMMITS.md (commit guidelines)
Provide next steps:
git commit -m "feat: add new feature"/versioning:bump to manually bump version/versioning:info to check current statusDisplay helpful commands:
/versioning:info status/versioning:bump patch