release-clio

Automate clio-agent releases with version bumping, CI checks, and asset publishing.

8|2|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/iowarp/clio-agent --skill release-clio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-clio
Source: https://github.com/iowarp/clio-agent/tree/main/.claude/skills/release-clio
Command: npx skills add https://github.com/iowarp/clio-agent --skill release-clio

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the release process for the clio-agent software, ensuring that all steps including version bumping, CI verification, and asset publishing are handled efficiently.

Core Features & Use Cases

  • Version Bumping: Automatically increments the version number of the clio-agent software.
  • CI Verification: Ensures that all Continuous Integration checks pass before the release.
  • Asset Publishing: Publishes the release assets to PyPI, GitHub Release, and ghcr.io container images.
  • Use Case: When preparing to release a new version of clio-agent, this Skill can be used to streamline the release process, saving time and reducing the potential for human error.

Quick Start

Run the release-clio skill to initiate the release process for clio-agent.

Frequently Asked Questions about release-clio

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

FAQPage Schema
How do I automate Python package release with CI verification and asset publishing?

Automating Python package release involves version bumping, verifying CI green status, and publishing artifacts to PyPI, GitHub Release, and ghcr.io container registries. This process ensures all continuous integration checks pass before deployment.

What does CI verification check before publishing software deployment artifacts?

CI verification checks continuous integration green status and validates artifacts before publishing. This ensures that all automated tests pass and build artifacts are correctly generated before triggering the release automation process.

How do I automate version bumping for Python 3.12 software deployment?

Automating version bumping for Python 3.12 software involves incrementing the version number programmatically during the release process. This ensures compatibility with Python 3.12+ environments and prepares the software for asset publishing.

Does release automation work with Git submodules for dependency management?

Release automation works with Git submodules for dependency management by integrating them into the release workflow. This ensures that submodule dependencies are correctly resolved and included during version bumping and asset publishing.

Can I publish release assets to PyPI, GitHub Release, and ghcr.io simultaneously?

You can publish release assets to PyPI, GitHub Release, and ghcr.io container images simultaneously through release automation. This multi-platform asset publishing occurs after CI verification confirms all checks pass.

What are the limitations of automating release processes for software deployment?

Limitations of automating release processes include dependency on CI green status checks and strict Python 3.12+ compatibility requirements. The release will fail if continuous integration checks do not pass or artifacts are invalid.