release

Propose, confirm, and execute software releases with SemVer and GitHub tagging.

1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/bildzeitung/lode --skill release-bildzeitung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/bildzeitung/lode/tree/main/.claude/skills/release
Command: npx skills add https://github.com/bildzeitung/lode --skill release-bildzeitung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, scripts/release.sh, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of proposing, confirming, and executing software releases, reducing the complexity and time required for release management.

Core Features & Use Cases

  • Version Proposal: Automatically suggest the next SemVer version based on commit history.
  • Release Notes Compilation: Compile release notes from resolved tickets in the release window.
  • Confirmation & Execution: Confirm the version and release notes, then execute the release script.
  • Use Case: Use this Skill to efficiently manage software releases in your project, ensuring that all steps are executed accurately and promptly.

Quick Start

Use the release skill to propose the next version and generate release notes for your project.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate SemVer versioning and GitHub tagging for my software release?

Automate SemVer versioning by analyzing commit history to propose the next version, compiling release notes, and executing GitHub tagging through an automated release script.

What's the best way to generate release notes from resolved tickets automatically?

Generate release notes by compiling resolved tickets within the release window, automatically extracting ticket data to create comprehensive notes for your software release.

How does SemVer version proposal work based on commit history?

SemVer version proposal works by analyzing your commit history to automatically suggest the next semantic version, ensuring accurate major, minor, or patch increments for software releases.

Do I need git and a release script to automate software releases?

Yes, git and a dedicated release script are required dependencies to automate software releases, enabling version confirmation and execution for GitHub tagging.

Can I confirm release notes before executing the final GitHub tagging?

Yes, you can review and confirm the proposed SemVer version and compiled release notes before executing the release script for final GitHub tagging.

Does this release management approach support automated execution after version confirmation?

Yes, after version confirmation, the release script executes the software release automatically, handling SemVer versioning and GitHub tagging without manual intervention.