dev-release

Generate changelogs, bump semver versions, commit, and tag git releases.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-release-evolutionapi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-release
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/dev-release
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-release-evolutionapi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the repetitive and error-prone steps of preparing a semantic version release by generating changelogs from git history, bumping manifest versions, creating git tags, and guiding verification checks.

Core Features & Use Cases

  • Changelog generation: Collects commits since the last tag and formats a new changelog section grouped by commit type when available.
  • Version determination and bumping: Reads common manifests (package.json, Cargo.toml, go.mod, pyproject.toml) to determine current version and propose major/minor/patch bumps.
  • Commit, tag, and push workflow: Updates manifests, commits with a release message, creates a tag, and optionally pushes after user confirmation while pairing with verification tools.
  • Pre-flight and verification: Enforces branch and workspace cleanliness checks, ensures tests/CI are green, and integrates with verifier skills for post-release validation.
  • Use Case: Ideal for preparing generic releases of libraries or non-EvoNexus projects where a consistent semver-based release process is required.

Quick Start

Run the dev-release skill to generate a changelog from recent commits, confirm a semver bump, update the project manifest, commit the change, and create a release tag.

Frequently Asked Questions about dev-release

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

FAQPage Schema
How do I automate generating a changelog from git commits before a release?

To automate changelog generation, this skill collects commits since the last git tag and formats them into a new changelog section grouped by commit type. It inspects your git history to produce a formatted changelog entry for your release.

How do I bump the version in my project manifest for a semver release?

To bump the version for a semver release, this skill reads manifests like package.json, Cargo.toml, go.mod, or pyproject.toml to determine the current version. It then proposes and applies a major, minor, or patch version bump to the manifest.

Does this release automation tool work with Python and Go projects?

Yes, this release automation tool works with Python and Go projects by reading pyproject.toml and go.mod files. It supports generic semver releases for any project using conventional manifests and git-based workflows.

What checks are required before creating a git tag for a version release?

Before creating a git tag for a version release, pre-flight checks enforce branch and workspace cleanliness and ensure tests or CI are green. This guarantees the repository is in a stable state before committing and tagging.

Can I automatically commit, tag, and push my release changes?

Yes, you can automatically commit, tag, and push your release changes. After updating the manifest version, this skill creates a release commit and git tag, then optionally pushes them to your remote repository after user confirmation.

What is the best way to manage semver versioning across different language projects?

The best way to manage semver versioning across different language projects is to use a tool that reads multiple manifest formats like package.json, Cargo.toml, go.mod, and pyproject.toml. This skill standardizes the release process across these environments.