version-sdlc

Automate version bumps, git tags, changelogs, and pushes for releases.

6|Updated Mar 4, 2026

Search Tags:#automation #changelog #versioning #semver #release-management #git-tag

Ready to run

npx skills add https://github.com/rnagrodzki/sdlc-marketplace --skill version-sdlc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: version-sdlc
Source: https://github.com/rnagrodzki/sdlc-marketplace/tree/main/plugins/sdlc-utilities/skills/version-sdlc
Command: npx skills add https://github.com/rnagrodzki/sdlc-marketplace --skill version-sdlc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Bump project versions, generate a release tag, and draft changelogs as part of an end-to-end release workflow using pre-computed context from skill/version.js.

Core Features & Use Cases

Consume pre-computed version context to perform an init setup or a full semantic release: bump version, create an annotated tag, optionally generate a CHANGELOG entry, commit, and push.
Support pre-release workflows and hotfix scenarios, including an auto mode to skip interactive prompts while still displaying the release plan.
Provide guardrails with pre-condition checks and error handling to ensure safe releases across common Git workflows and project configurations.

Quick Start

Invoke the skill with a bump type (major|minor|patch) and optional flags to start a release workflow.

Frequently Asked Questions about version-sdlc

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

FAQPage Schema

How do I automate semantic versioning and changelog generation for git releases?▼

You can automate semantic versioning and changelog generation by bumping the project version, creating an annotated git tag, optionally generating a CHANGELOG entry, and pushing the commit. This end-to-end release workflow relies on pre-computed version context to ensure safe, consistent semantic releases.

What is the best way to create an automated pre-release or hotfix workflow in git?▼

The best way to create an automated pre-release or hotfix workflow is to invoke the release process with dedicated flags like --pre or --hotfix. These trigger specific release scenarios that safely bump versions and apply git tags based on pre-computed context, while --auto mode skips interactive prompts for non-interactive runs.

How do I skip interactive prompts during an automated release and changelog bump?▼

To skip interactive prompts during an automated release and changelog bump, you use the --auto flag. This mode executes the end-to-end semantic versioning workflow non-interactively while still displaying the release plan for verification before performing git operations.

Does automated release management work without pushing commits to the remote repository?▼

Yes, automated release management can work without pushing commits to the remote repository by applying the --no-push flag. This allows you to locally bump the semantic version, generate the changelog entry, and create the annotated git tag while preventing any remote repository updates.

What pre-conditions are checked before executing git operations for a semantic release?▼

Before executing git operations for a semantic release, pre-condition checks and error handling guardrails are enforced. These checks verify the required pre-computed version context and validate the environment to ensure safe releases across common Git workflows and project configurations.

Do I need a specific file to initialize automated semantic versioning and tagging?▼

Yes, you need pre-computed version context from skill/version.js to initialize automated semantic versioning and tagging. The --init flag triggers the setup process, consuming this specific context to safely perform version bumps and generate annotated git tags within your project.