velesdb-release

Enforce SemVer compliance and publish VelesDB releases to crates.io, PyPI, and npm.

84|9|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/cyberlife-coder/VelesDB --skill velesdb-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: velesdb-release
Source: https://github.com/cyberlife-coder/VelesDB/tree/main/.claude/skills/velesdb-release
Command: npx skills add https://github.com/cyberlife-coder/VelesDB --skill velesdb-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates VelesDB version releases with SemVer compliance, comprehensive documentation audit, changelog generation, local CI validation, and multi-platform publishing (crates.io, PyPI, npm), reducing release drift and manual toil.

Core Features & Use Cases

  • SemVer validation: Enforces semantic versioning rules for every release.
  • Changelog automation: Generates and aggregates user-facing changelog entries from commits.
  • CI integration: Validates build, tests, and packaging in a release workflow.
  • Multi-platform publishing: Publishes to crates.io, PyPI, and npm, with tag creation and GitHub Releases.
  • Documentation audit: Ensures docs are up-to-date, with last-updated timestamps and version references refreshed.

Quick Start

Run velesdb-release with the target SemVer version and release type to start a new release workflow.

Frequently Asked Questions about velesdb-release

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

FAQPage Schema
How do I automate multi-platform publishing to crates.io, PyPI, and npm?

Automate multi-platform publishing by coordinating deployments to crates.io, PyPI, npm, and GitHub Releases. This release management workflow enforces SemVer compliance, requires a validated changelog, and validates CI workspace checks to guarantee clean, reproducible package distribution.

What is the best way to enforce SemVer compliance during version bumps?

Enforce SemVer compliance by validating semantic versioning rules before any release preparation. The workflow audits version references, checks the workspace, and requires a validated changelog to prevent invalid version increments from reaching the multi-platform deployment pipeline.

How do I generate and validate a changelog from commits for a release?

Generate a changelog by aggregating user-facing entries from commits during release preparation. The workflow validates the changelog, audits documentation timestamps, and refreshes version references to ensure release notes are accurate before publishing.

Does CI integration matter for reproducible releases?

CI integration is critical for reproducible releases because it validates builds, tests, and packaging within the release workflow. Requiring workspace checks and CI validation eliminates manual toil and prevents release drift across deployment environments.

Can I use this release workflow without updating my documentation?

You cannot release without updating documentation because the workflow performs a comprehensive documentation audit. The process ensures docs are up-to-date by refreshing last-updated timestamps and version references, guaranteeing clean, reproducible releases across all platforms.