release-core

Automates versioning, changelog creation, tagging, CI/CD deployment for mx-core projects.

547|153|Updated Jul 14, 2021
One-click install
npx skills add https://github.com/mx-space/core --skill release-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-core
Source: https://github.com/mx-space/core/tree/main/.claude/skills/release-core
Command: npx skills add https://github.com/mx-space/core --skill release-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires conventional-changelog-cli, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the release process for mx-core projects by automating version bumping, changelog generation, tagging, and deployment steps, reducing manual effort and errors.

Core Features & Use Cases

  • Version Management: Automates version bumping and tagging based on commit history.
  • Changelog Automation: Generates standardized changelog entries from recent commits.
  • Deployment Integration: Triggers Docker builds and production redeployment after release.
  • Use Case: A developer wants to release a new feature update; this Skill handles all steps from updating version numbers to pushing tags and deploying the new release seamlessly.

Quick Start

Use this Skill to prepare and execute a new release for the mx-core server by updating version, generating changelog, tagging, and pushing changes.

Frequently Asked Questions about release-core

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

FAQPage Schema
How do I automate server release workflows with version bump and changelog generation?

Automate server release workflows by executing scripts that handle version bumping, generate standardized changelog entries from commit history, apply git tags, and trigger deployment. This ensures consistent, error-free releases without manual intervention.

How does conventional-changelog-cli integrate with automated deployment processes?

Conventional-changelog-cli integrates by automatically parsing recent git commit history to generate standardized changelog entries. These entries are then committed alongside version bumps before triggering Docker builds and production redeployment.

Can I use this release automation for both server and API client projects?

Yes, the release automation supports conditional execution tailored for both server and API client projects. It enforces safe practices with built-in checks and manual confirmations to ensure appropriate deployment steps for each project type.

Do I need gh and conventional-changelog-cli installed to automate version bumps and tagging?

Yes, both gh and conventional-changelog-cli are required dependencies to automate version bumps and tagging. Gh handles repository interactions and releases, while conventional-changelog-cli parses commit history to generate the changelog.

What is the best way to trigger a Docker redeployment after a version bump?

The best way to trigger Docker redeployment is to let the release workflow handle it automatically after confirming the version bump and tag push. The automation ensures Docker builds are triggered only after successful changelog generation and tagging.

Why does the deployment process require manual confirmation during release?

Manual confirmation is required during release to enforce safe practices and prevent erroneous deployments. The automation pauses for user validation at critical steps, ensuring checks pass before proceeding with irreversible actions like tagging or production deployment.