version-release

Automate versioned release workflows with version bumps, changelog updates, tags, and GitHub releases.

4|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill version-release-laitszkin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-release
Source: https://github.com/LaiTszKin/apollo-toolkit/tree/main/version-release
Command: npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill version-release-laitszkin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill guides teams and agents to perform repeatable, compliant versioned releases, ensuring that version bumps, changelogs, tags, and GitHub releases are executed in a safe, auditable manner.

Core Features & Use Cases

  • Release scope assessment and alignment with project docs.
  • Conditional execution of archival steps (archive-specs) to convert completed specs into standardized, categorized project docs before finalizing a release.
  • End-to-end release tasks: bump version files, update changelog, commit changes, create and push tags, and publish the GitHub release.

Quick Start

Invoke the skill with an explicit release request to bump versions, update changelogs, create tags, publish a GitHub release, and push changes.

Frequently Asked Questions about version-release

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

FAQPage Schema
How do I automate version bumps and GitHub release publishing?

To automate version release publishing, you invoke the skill with an explicit release request to bump version files, update changelogs, commit, create tags, and push GitHub releases safely.

What is the best way to update changelogs and create git tags for a release?

The best way to update changelogs and create git tags is through an automated end-to-end release workflow that assesses release scope, edits the changelog, commits changes, and creates tags.

Does this release management workflow require explicit intent to publish?

Yes, this release management workflow requires explicit release intent to safely coordinate version bumps, changelog updates, and GitHub release publication across codebases and project docs.

Can I convert specs into project docs before finalizing a GitHub release?

Yes, you can convert specs into standardized project docs before finalizing a release by applying the conditional archive-specs archival step during the version release workflow.

When should I coordinate security checks during a version release?

You should coordinate security checks during a version release when handling code-affecting work, coordinating with dependencies like harden-app-security to ensure safe, compliant releases.