minecraft-agent-skills: Skill for Claude Code

Minecraft CI / Release Skill

Routing Boundaries

• Use when: the task is CI/CD pipelines, artifact publishing, versioning, or release management.
• Do not use when: the task is gameplay or plugin implementation (minecraft-modding, minecraft-plugin-dev, or minecraft-datapack).
• Do not use when: the task is server runtime operations or infrastructure tuning (minecraft-server-admin).

---

Release setup

Keep each repository's existing release destinations and approval policy. A tag can build an artifact and create a GitHub Release without publishing to Modrinth or CurseForge. Add a publisher only when the project already uses it or the user asks for it. Never add tokens to committed files.

For Minecraft 26.x, use Java 25 and state that in workflow labels and examples. Legacy Minecraft 1.21.x projects stay on Java 21; retain their own loader and Gradle conventions instead of mechanically changing their version.

Use an immutable GitHub Action revision in a protected workflow. The following refs were verified from the upstream tags on 2026-10-29; refresh them from the upstream tag before intentionally upgrading an action:

actions/[email protected]             3d3c42e5aac5ba805825da76410c181273ba90b1
actions/[email protected]           dd06d9cba3e5552c54d9f8ea23572deb30010f7c
gradle/actions/[email protected]  9c971963bec38e04b3d30dcc455b5382be2fdbfb
actions/[email protected]      043fb46d1a93c77aae656e7c1c64a875d1fc6a0a
softprops/[email protected]  efb35369e0ad2afab669f228072c1b0d510eae64

Version and Tag Convention

When the project uses a Minecraft-version suffix, follow {mod_version}+{mc_version}:

1.0.0+26.3  ← mod 1.0.0 for MC 26.3
1.2.3+26.3
2.0.0+26.3

Use a release version without the game suffix for the Git tag, and retain the Minecraft version in the artifact version when the project uses that convention:

mod_version: 1.2.3
project/artifact version: 1.2.3+26.3
tag: v1.2.3

The release workflow must verify that v1.2.3 matches mod_version=1.2.3 before building. Do not override mod_version from the tag, because that hides a mismatch. The Gradle task and safe changelog extraction are in the publishing reference.