release

Detect current version, generate a Keep a Changelog entry, and bump version files.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill release-bingeli1379
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/bingeli1379/eli-claude-marketplace/tree/main/plugins/eli-tools/skills/release
Command: npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill release-bingeli1379

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates release management by detecting the current project version, generating a user-friendly changelog, and bumping the version number to keep releases consistent.

Core Features & Use Cases

  • Automatic version detection: scans npm, .NET, Python, Rust, Go, or plain version files to identify the current release version.
  • Changelog generation: creates a Keep a Changelog–style entry that highlights added, changed, or fixed items.
  • Automatic version bump and commit: updates the version file(s) and commits changes with a conventional message.

Quick Start

Initiate the release workflow to detect the current version, generate a changelog, and bump the version.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumping and changelog generation across multiple programming languages?

Automate version bumping and changelog generation by parsing version files across npm, .NET, Python, Rust, Go, or plain version.txt to detect the current release and apply an automatic version bump.

Can I generate a Keep a Changelog style entry automatically from my git history?

Yes, you can generate a Keep a Changelog style entry automatically by determining the baseline from your git history and creating entries that highlight added, changed, or fixed items.

Does automated release management work with both Cargo.toml and Directory.Build.props files?

Automated release management works with Cargo.toml and Directory.Build.props files, scanning each specific format to identify the current project version and update it during the release workflow.

What is the best way to trigger an automated version bump in a CI pipeline?

The best way to trigger an automated version bump in CI is to initiate the release workflow, which detects the current version, generates a changelog, bumps the version, and commits changes with a conventional message.

How do I ensure my release workflow commits the updated version file automatically?

Ensure your release workflow commits the updated version file automatically by using the built-in commit feature, which writes the bumped version and changes back with a conventional commit message.

What happens if my project has no existing changelog baseline for version detection?

If no existing changelog baseline is present for version detection, the release workflow determines the baseline directly from git history to accurately calculate and apply the next version bump.