release-process

Automate emoji_gen versioning, tagging, CI deployment, and artifact validation with Git, Cargo, Docker, and GitHub CLI workflows.

Updated Dec 20, 2025

Search Tags:#git #versioning #release #docker #cargo #ci

Ready to run

npx skills add https://github.com/francisfuzz/emoji_gen --skill release-process

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/francisfuzz/emoji_gen/tree/main/.claude/skills/release-process
Command: npx skills add https://github.com/francisfuzz/emoji_gen --skill release-process

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides emoji_gen releases, covering version bumps, tagging, CI deployment, and release notes to ensure reliable, repeatable distribution.

Core Features & Use Cases

Semantic versioning guidance and decision rules
Step-by-step release workflow (update Cargo.toml, commit, tag, push, monitor CI)
Release artifacts verification and multi-platform publishing

Quick Start

Prepare a release by determining the version, updating Cargo.toml, creating and pushing a tag, and monitoring CI as described in this Skill.

Frequently Asked Questions about release-process

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

FAQPage Schema

How do I automate version bumping and tagging for a Cargo project release?▼

Automate version bumping by updating Cargo.toml with the new semantic version, committing the change, creating an annotated Git tag, and pushing both to trigger CI deployment. This Skill guides the full workflow from version decision through artifact verification across platforms.

What's the best way to build and publish multi-platform binaries and Docker images in a CI pipeline?▼

Use annotated Git tags to trigger CI workflows that build binaries for multiple platforms and Docker images simultaneously. This Skill handles the release process including artifact validation and checksums, automating distribution through GitHub releases.

How do I ensure semantic versioning is applied correctly when releasing a project?▼

Semantic versioning determines whether you increment major, minor, or patch versions based on breaking changes, new features, or bug fixes. This Skill provides decision rules and step-by-step guidance to apply versioning consistently before tagging and deploying releases.

Can I use Docker and Cargo together in an automated release workflow?▼

Yes. This Skill automates releases that build Cargo binaries and Docker images together, validating both artifact types and creating GitHub releases with checksums. Requires Git, Cargo, Docker, GitHub CLI, and repository release workflow access.

What prerequisites do I need before starting a release process?▼

You need Git, Cargo, Docker, GitHub CLI installed; write access to the repository; and an existing release workflow configured in CI. The Skill automates the workflow once these tools and permissions are in place.

Why should I use annotated tags instead of lightweight tags for releases?▼

Annotated tags store metadata, create audit history, and integrate with CI systems to trigger automated deployment pipelines. This Skill uses annotated tags to ensure releases are reliably tracked and reproducible across platforms.