skills.rest
evolution-foundation
evolution-foundationOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dev-release

Generate a changelog, bump semantic versions, and create a release commit and tag.

520|175|Updated Apr 8, 2026
Search Tags:#changelog#release#semantic versioning#project maintenance#version bump#CI verification#git tagging
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-release-evolution-foundation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-release
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-release
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-release-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the release preparation process by automating changelog generation, semantic version bumping, and creation of a Git tag so teams can publish updates consistently.

Core Features & Use Cases

  • Pre-flight validation: Ensures you are on the correct branch, with a clean working tree, green CI, and passing local tests before proceeding.
  • Version determination: Reads the current version from the project manifest and supports major, minor, or patch semver bumps with explicit confirmation.
  • Changelog and release artifacts: Builds a new CHANGELOG.md section from git history and creates the release commit and tag, then verifies correctness with a dedicated verifier workflow.

Quick Start

Use dev-release to prepare a non-EvoNexus project release by confirming the proposed semver bump and then generating the changelog and tag from commits since the last tag.

Frequently Asked Questions about dev-release

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

FAQPage Schema
How do I generate a changelog from git history for a new release?▼

This Skill automates changelog generation by grouping commits since the last tag into a new CHANGELOG.md section, then creating the release commit and tag.

What's the best way to automate semantic version bumps and git tagging?▼

Automating semantic version bumps requires reading the current project manifest version, applying a major, minor, or patch bump with explicit confirmation, and pushing a verified git tag.

Do I need a clean working tree and passing CI to create a release tag?▼

Yes, creating a release tag requires a clean working tree, green CI, and passing local tests, as this Skill performs pre-flight validation to ensure release readiness.

Can I use this automated release process for any project repository?▼

This automated release process applies specifically to library and tooling repositories that follow a conventional version manifest and a git-based tagging workflow.

How does version bump verification work during release preparation?▼

Version bump verification works by confirming the proposed semver bump, creating the release commit and tag, and running a final correctness check via a dedicated oath verifier workflow.

Related Skills

Explore More Software Engineering Skills→
joa23joa23
142

release

Automate pre-release validation of changelog, versioning, tests, and documentation.

Community
Intermediate
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
gittowergittower
413

release

Update changelog and version files from git history using semantic versioning.

Official
Advanced
jankneumannjankneumann
4

changelog-version

Analyze Git history to generate changelog entries and semantic version bumps.

Community
Advanced