release

Automate VibeFrame version bumps, changelog generation, and commit staging.

164|31|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/vericontext/vibeframe --skill release-vericontext
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/vericontext/vibeframe/tree/main/.agents/skills/release
Command: npx skills add https://github.com/vericontext/vibeframe --skill release-vericontext

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of bumping VibeFrame versions, regenerating release artifacts, running verification, and preparing a version commit, saving time and reducing human error in the release process.

Core Features & Use Cases

  • Version Bumping: Automatically bumps VibeFrame versions to patch, minor, or major based on commit types.
  • Release Artifacts: Regenerates release artifacts and prepares a version commit.
  • Verification: Runs verification steps to ensure all package versions match and the release is ready.
  • Use Case: When a new feature or fix is committed to the VibeFrame repository, this Skill can be used to automate the release process, ensuring consistency and efficiency.

Quick Start

Run the release skill to automate the version bumping and release preparation for VibeFrame.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm version bumping and changelog generation for my repository?

The release Skill automates version bumping by evaluating commit types to determine patch, minor, or major increments, regenerates release artifacts, runs verification, and stages the commit. This saves time and reduces human error in the release process.

What's the best way to prepare a release commit and ensure package versions match?

Use an automated release workflow that runs verification steps to ensure all package versions match before staging. This guarantees consistency across the repository and validates that the release is ready before creating the commit.

Do I need npm and git installed to automate my CI/CD release process?

Yes, you need npm and git installed to automate your CI/CD release process, along with various CI/CD tools for execution and validation. These dependencies are required to coordinate version updates and prepare commits.

How does automated version bumping decide between patch, minor, and major releases?

Automated version bumping decides between patch, minor, and major releases based on commit types. The system evaluates the commit history to apply the correct semantic versioning increment automatically when new features or fixes are committed.

Can I use release automation to regenerate artifacts and run verification before committing?

Yes, you can use release automation to regenerate artifacts and run verification before committing. The workflow coordinates artifact regeneration and validation steps to ensure all package versions match before staging the commit.

Why does my release workflow fail verification when package versions do not match?

Your release workflow fails verification when package versions do not match because the verification step explicitly checks for version consistency. Automated version bumping resolves this by updating all package versions together before staging the commit.