qol-cicd

Standardize CI, versioning, and releases across qol repositories with shared GitHub Actions workflows.

Updated Apr 19, 2026

Search Tags:#automation #versioning #release-management #github-actions #ci-cd #workflows

Ready to run

npx skills add https://github.com/qol-tools/qol-skills --skill qol-cicd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qol-cicd
Source: https://github.com/qol-tools/qol-skills/tree/main/plugins/qol-ecosystem/skills/qol-cicd
Command: npx skills add https://github.com/qol-tools/qol-skills --skill qol-cicd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and enforces CI/CD, versioning, and release standards across qol repos to prevent drift and duplication.

Core Features & Use Cases

Centralized reusable workflows for versioning and releases used by qol repos.
Clear release contracts that govern Linux and macOS release behavior and optional signing.
Use Case: When releasing a qol-tray update, run the shared workflows to increment version, tag releases, and publish artifacts across all affected repos.

Quick Start

Configure and invoke the reusable release workflows in your repository to begin automated versioning and publishing.

Frequently Asked Questions about qol-cicd

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

FAQPage Schema

How do I standardize CI/CD workflows across multiple GitHub repositories?▼

To standardize CI/CD workflows across multiple GitHub repositories, use centralized reusable GitHub Actions workflows that enforce consistent versioning and release contracts, preventing configuration drift and duplication across all affected repos.

How do I automate versioning and release tagging for shared GitHub Actions workflows?▼

Automate versioning and release tagging for shared GitHub Actions workflows by invoking the centralized plugin-version workflow, which increments version numbers, tags releases, and publishes artifacts consistently across all affected repositories.

Can I configure conditional macOS release signing using GitHub Actions secrets?▼

Yes, you can configure conditional macOS release signing using GitHub Actions secrets. The centralized release contracts support conditional macOS releases with optional signing secrets to handle platform-specific publishing requirements securely.

What is the best way to manage release contracts for Linux and macOS artifacts?▼

The best way to manage release contracts for Linux and macOS artifacts is through a centralized CI/CD workflow that governs platform-specific release behavior, ensuring consistent versioning and optional macOS signing across all repositories.

Why do my automated release workflows keep drifting between different repositories?▼

Automated release workflows drift between different repositories when CI/CD configurations are duplicated locally. Centralizing reusable GitHub Actions workflows and enforcing shared release contracts prevents this drift and maintains version consistency across all repos.