adv-ci-release

Automate release lifecycle with semver versioning and GitHub releases.

4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Sharper-Flow/Advance --skill adv-ci-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adv-ci-release
Source: https://github.com/Sharper-Flow/Advance/tree/main/skills/adv-ci-release
Command: npx skills add https://github.com/Sharper-Flow/Advance --skill adv-ci-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual overhead of versioning, changelog maintenance, and binary distribution by automating the entire release lifecycle based on conventional commit messages.

Core Features & Use Cases

  • Automated Semver: Automatically calculates major, minor, or patch version bumps based on commit history.
  • Release Orchestration: Generates changelogs, builds cross-platform binaries, and publishes GitHub releases upon successful CI completion.
  • Use Case: A developer pushes a feature branch to trunk; the skill automatically validates the code, bumps the version, updates the changelog, and deploys release artifacts without human intervention.

Quick Start

Apply the adv-ci-release pattern to this repository by configuring the CI and auto-release workflow files and ensuring all commits follow the conventional commit specification.

Frequently Asked Questions about adv-ci-release

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

FAQPage Schema
How do I automate semver releases and changelog generation in GitHub Actions?

Automated semver releases calculate version bumps from conventional commit messages to trigger changelog generation, cross-platform binary builds, and GitHub release creation within GitHub Actions pipelines.

What is the best way to trigger automatic version bumps from conventional commit messages?

Triggering automatic version bumps requires parsing conventional commit history to apply deterministic semver logic, ensuring patch, minor, or major releases execute without manual intervention.

Does automated release orchestration work for cross-platform binary builds and checksum validation?

Automated release orchestration builds cross-platform binaries and validates artifact integrity via checksums upon successful CI completion to ensure deterministic release gates for public repositories.

Can I use automated semver release workflows for my public software repository?

Automated semver release workflows target public software repositories, requiring commits to follow the conventional commit specification to properly parse versioning logic and distribute artifacts.

How do I set up deterministic release gates for CI/CD pipelines?

Deterministic release gates apply standardized versioning logic and artifact distribution upon successful CI completion, ensuring release orchestration only triggers when validation passes.

Why do automated changelog releases require conventional commit specifications?

Automated changelog releases require conventional commit specifications to accurately parse commit history, enabling the system to determine the correct semver bump and generate standardized release notes.