cicd

Manage GitHub release pipelines from develop branches to production tags.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/messeb/skills --skill cicd-messeb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cicd
Source: https://github.com/messeb/skills/tree/main/plugins/general-developer/skills/cicd
Command: npx skills add https://github.com/messeb/skills --skill cicd-messeb

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates and guides developers through the complex process of managing software releases, from initial development branches to production deployment, ensuring consistency and reducing manual errors.

Core Features & Use Cases

  • Full Release Lifecycle Management: Manages the developrelease/x.y.zvX.Y.Z-rc.NvX.Y.Z flow.
  • Automated Workflow Triggers: Integrates with GitHub Actions for CI, RC builds, and production deployments.
  • Use Case: When a developer wants to prepare a new version for release, this Skill helps them create the correct release branch, tag release candidates, and finally promote the stable version to production.

Quick Start

Guide me through starting a new release for version 1.5.0.

Frequently Asked Questions about cicd

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

FAQPage Schema
How do I manage a GitHub release pipeline from a develop branch to production?

Managing a GitHub release pipeline involves creating release branches, tagging release candidates, and promoting to production. This workflow automates the develop to release branch to RC tags to production tag flow using GitHub Actions.

How do I tag release candidates for a new software version?

Tagging release candidates requires creating a release branch named release/x.y.z and applying vX.Y.Z-rc.N tags. This process is managed through automated CI/CD integration to ensure consistent candidate management before final deployment.

Does this release management workflow support Docker image promotion for production deployments?

Yes, Docker image promotion is supported for production deployments. The workflow promotes stable versions to production by coordinating Docker image promotion alongside final production tags triggered via GitHub Actions.

What is the best way to automate CI/CD integration for release versioning?

Automating CI/CD integration for release versioning is best handled by triggering GitHub Actions workflows for CI, RC builds, and production deployments. This ensures consistent versioning and coordination across the full release lifecycle.

Can I use this workflow to coordinate deployment across multiple release branches?

Yes, you can coordinate deployment across multiple release branches. The workflow supports creating distinct release branches for different versions, managing independent release candidates, and automating their respective paths to production.