release-process

Automate end-to-end release workflows for npm, Python, and Rust projects.

3|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/cloga/optimus-code --skill release-process-cloga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/cloga/optimus-code/tree/main/optimus-plugin/skills/release-process
Command: npx skills add https://github.com/cloga/optimus-code --skill release-process-cloga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generic, config-driven release processes for software projects, covering version bumps, changelogs, builds, documentation updates, tagging, and publishing across npm, Python, and Rust.

Core Features & Use Cases

  • End-to-end release orchestration for multi-language projects.
  • Auto-detection of project type and appropriate release steps based on configuration.
  • Safe, auditable release with changelog generation, build, and publish support.

Quick Start

Invoke the release-process skill to automate version bumps, changelog updates, builds, tagging, and publishing across npm, Python, and Rust projects.

Frequently Asked Questions about release-process

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

FAQPage Schema
How do I automate version bumps and changelog generation for npm and Python projects?▼

To automate release workflows, the release-process skill handles version bumps and changelog generation for npm, Python, and Rust projects. It auto-detects project types and orchestrates builds, tagging, and publishing.

What is config-driven release automation and how does it work?▼

Config-driven release automation uses optional configuration files like .optimus/config/release-config.json to define release steps. When fields are omitted, the system auto-detects project specifics to handle versioning, builds, and publishing.

Can I publish Rust crates and npm packages without writing custom release scripts?▼

Yes, you can publish Rust crates and npm packages without custom scripts. The skill manages end-to-end release orchestration, automatically detecting the language and executing the appropriate build and publish steps.

Does the release process support auto-detection when I omit configuration fields?▼

Yes, the release process supports auto-detection when configuration fields are omitted. It reads optional .optimus/config/release-config.json and automatically infers project type and appropriate release steps for npm, Python, or Rust.

What is the best way to manage multi-language release orchestration across npm, Python, and Rust?▼

The best way to manage multi-language release orchestration is using a config-driven skill that standardizes version bumps, changelog updates, documentation generation, and publishing across npm, Python, and Rust projects.

Do I need to manually update documentation and tags when automating software releases?▼

No, you do not need to manually update documentation and tags. The release automation skill handles documentation updates and git tagging automatically as part of its end-to-end release workflow.