release-workflow

Automate software releases across Rust, Node.js, Python, and Go ecosystems.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill release-workflow-takemo101
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-workflow
Source: https://github.com/takemo101/compose-workflow/tree/main/.opencode/skill/release-workflow
Command: npx skills add https://github.com/takemo101/compose-workflow --skill release-workflow-takemo101

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire software release process, from checking version consistency and proposing new versions to creating GitHub Releases, ensuring a smooth and error-free deployment.

Core Features & Use Cases

  • Automated Versioning: Detects ecosystem (Rust, Node.js, Python, Go, etc.) and suggests semantic version bumps.
  • Integrity Checks: Scans for hardcoded versions in code and documentation to prevent inconsistencies.
  • Release Automation: Handles version file updates, changelog generation, Git tagging, and GitHub Release creation.
  • Use Case: A developer needs to release a new version of their Rust application. They run this Skill, which automatically detects the Cargo.toml file, suggests a version bump based on commit messages, checks for hardcoded versions in README.md, updates Cargo.toml and CHANGELOG.md, creates a Git tag, and publishes a GitHub Release.

Quick Start

Run the release script to automate the release process for the current project.

Frequently Asked Questions about release-workflow

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

FAQPage Schema
How do I automate semantic versioning and GitHub Release creation across multiple ecosystems?

Automate semantic versioning and GitHub Release creation by detecting project ecosystems like Rust, Node.js, Python, and Go, proposing version bumps, updating version files, generating changelogs, and creating Git tags.

How does automated release workflow handle version integrity checks?

Automated release workflow handles version integrity checks by scanning code and documentation for hardcoded versions to prevent inconsistencies before proposing semantic version bumps and updating version files.

Can I use this release automation tool with Rust, Node.js, Python, and Go projects?

Yes, this release automation tool supports Rust, Node.js, Python, and Go projects by automatically detecting the project ecosystem and its corresponding version files like Cargo.toml.

What is the best way to manage changelog updates and Git tagging during software deployment?

The best way to manage changelog updates and Git tagging during software deployment is using an end-to-end release automation workflow that handles version file updates, changelog generation, and Git tag creation.

Why do hardcoded versions in README files cause release automation failures?

Hardcoded versions in README files cause release automation failures because they break version integrity checks, so the workflow scans documentation to prevent inconsistencies before finalizing the deployment.