minecraft-ci-release

Automate Minecraft CI and release workflows for Fabric, NeoForge, and Paper projects.

2|Updated May 22, 2026
One-click install
npx skills add https://github.com/AIKUSAN/minecraft-agent-skills-bundle --skill minecraft-ci-release-aikusan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: minecraft-ci-release
Source: https://github.com/AIKUSAN/minecraft-agent-skills-bundle/tree/main/plugins/minecraft-codex-skills/skills/minecraft-ci-release
Command: npx skills add https://github.com/AIKUSAN/minecraft-agent-skills-bundle --skill minecraft-ci-release-aikusan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the manual overhead of building, testing, packaging, and publishing Minecraft mods and plugins so release work stays consistent and repeatable.

Core Features & Use Cases

  • End-to-end release automation: Orchestrates pull request checks, main-branch builds, and tag-triggered publish pipelines for Fabric, NeoForge, and Paper projects.
  • Artifact publishing: Supports Modrinth, CurseForge, and GitHub Releases with version extraction, changelog generation, and multi-platform JAR uploads.
  • Release governance: Encodes semantic versioning rules, Dependabot upkeep, build caching, and branch protection expectations for production-grade delivery.
  • Validation tooling: Includes a script to verify workflow snippets in the skill file and catch malformed YAML, unresolved placeholders, and secret usage issues.

Quick Start

Use the minecraft-ci-release skill to design a GitHub Actions release pipeline for a Minecraft project that builds on pull requests, publishes tagged releases, and uploads artifacts to Modrinth, CurseForge, and GitHub Releases.

Frequently Asked Questions about minecraft-ci-release

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

FAQPage Schema
How do I automate Minecraft mod releases to Modrinth and CurseForge using GitHub Actions?

Automate Minecraft mod releases by configuring GitHub Actions pipelines that extract semantic versions, generate changelogs, and upload JARs to Modrinth and CurseForge using secret-backed credentials.

Can I use this CI release automation for Fabric, NeoForge, and Paper projects?

Yes, this CI release automation supports Fabric, NeoForge, and Paper projects, orchestrating pull request checks, branch builds, and tag-triggered publish pipelines across all three platforms.

What do I need to set up before automating Gradle build and publish tasks for Minecraft mods?

You need GitHub Actions, Gradle build and publish tasks, semantic versioning rules, build caching, Dependabot upkeep, and secret-backed Modrinth and CurseForge credentials configured before automating Minecraft releases.

How does the validation script catch malformed YAML in GitHub Actions release workflows?

The validation script verifies workflow snippets to catch malformed YAML, unresolved placeholders, and secret usage issues, ensuring your Minecraft CI release pipelines function correctly before execution.

What is the best way to manage semantic versioning and changelog extraction for Minecraft plugin releases?

Manage semantic versioning and changelog extraction by encoding release governance rules into your CI pipeline, automatically pulling version tags and changelog text during tag-triggered GitHub Actions workflows.

Why are my Minecraft mod artifacts failing to publish during CI release automation?

Artifact publishing failures often stem from unresolved placeholders, malformed YAML, or incorrect secret-backed Modrinth and CurseForge credentials, which the included validation script helps identify and resolve.