release

Orchestrate software releases with versioning, Git tags, and workflow verification.

3.2k|690|Updated Aug 25, 2025
One-click install
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill release-devin-axis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/release
Command: npx skills add https://github.com/Devin-AXIS/iPolloWork --skill release-devin-axis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages the complexity of software release processes by providing a streamlined flow for versioning, tagging, and verifying changes before deploying a release.

Core Features & Use Cases

  • Version Management: Bump and update version numbers in various files and directories.
  • Tagging: Automates the creation and pushing of Git tags to trigger release workflows.
  • Reruns & Verification: Supports rerunning workflows if necessary and verifies the deployment and published release.

Quick Start

Run the release skill with the version tag 'vX.Y.Z' to automate the release process.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate versioning and Git tag creation for a software release?

To automate software release versioning and Git tag creation, you need a streamlined flow that bumps version numbers, creates tags, and pushes them to trigger pre-configured workflows. This ensures consistent version management across project files.

What is the best way to verify a deployment after pushing a release tag?

Verifying a deployment after pushing a release tag involves checking the workflow execution status and confirming the published release outcome. A complete release flow supports rerunning workflows if necessary and validates the final deployment.

Do I need pre-configured Git workflows to automate my release process?

Yes, automating a release process requires a Git repository with pre-configured workflows for release automation. The flow orchestrates version bumping and tagging to trigger these existing workflows, rather than building them from scratch.

Can I rerun a failed release workflow without starting the versioning process over?

Yes, you can rerun failed release workflows without repeating the versioning process. The release flow supports rerunning workflows directly if initial executions fail, allowing you to verify the deployment outcome without redundant version bumps.

How do I update version numbers across multiple files before creating a Git release tag?

Updating version numbers across multiple files before creating a Git release tag is handled by version management automation. It bumps and synchronizes version strings in various project directories, then proceeds to tag creation and workflow triggering.