Release
sol4k/sol4k
Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.
Set up and review CI, artifact publishing, versioning, and release management for Minecraft 26.x or legacy 1.21.x mods and Paper plugins.
$ npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-ci-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jahrome907/minecraft-agent-skills minecraft-ci-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jahrome907/minecraft-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/minecraft-ci-release .claude/skills/minecraft-ci-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "minecraft-ci-release" agent skill from https://github.com/Jahrome907/minecraft-agent-skills/tree/main/.codex/skills/minecraft-ci-release into .claude/skills/minecraft-ci-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "minecraft-ci-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Jahrome907/minecraft-agent-skills/tree/main/.codex/skills/minecraft-ci-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-ci-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jahrome907/minecraft-agent-skills minecraft-ci-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jahrome907/minecraft-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/minecraft-ci-release .agents/skills/minecraft-ci-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "minecraft-ci-release" agent skill from https://github.com/Jahrome907/minecraft-agent-skills/tree/main/.codex/skills/minecraft-ci-release into .agents/skills/minecraft-ci-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "minecraft-ci-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-ci-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jahrome907/minecraft-agent-skills minecraft-ci-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jahrome907/minecraft-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/minecraft-ci-release .cursor/skills/minecraft-ci-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "minecraft-ci-release" agent skill from https://github.com/Jahrome907/minecraft-agent-skills/tree/main/.codex/skills/minecraft-ci-release into .cursor/skills/minecraft-ci-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "minecraft-ci-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Jahrome907/minecraft-agent-skills.git --path .codex/skills/minecraft-ci-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-ci-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jahrome907/minecraft-agent-skills minecraft-ci-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jahrome907/minecraft-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/minecraft-ci-release .gemini/skills/minecraft-ci-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "minecraft-ci-release" agent skill from https://github.com/Jahrome907/minecraft-agent-skills/tree/main/.codex/skills/minecraft-ci-release into .gemini/skills/minecraft-ci-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "minecraft-ci-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Jahrome907/minecraft-agent-skills minecraft-ci-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-ci-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jahrome907/minecraft-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/minecraft-ci-release .github/skills/minecraft-ci-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "minecraft-ci-release" agent skill from https://github.com/Jahrome907/minecraft-agent-skills/tree/main/.codex/skills/minecraft-ci-release into .github/skills/minecraft-ci-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "minecraft-ci-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-ci-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jahrome907/minecraft-agent-skills minecraft-ci-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jahrome907/minecraft-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/minecraft-ci-release .opencode/skills/minecraft-ci-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "minecraft-ci-release" agent skill from https://github.com/Jahrome907/minecraft-agent-skills/tree/main/.codex/skills/minecraft-ci-release into .opencode/skills/minecraft-ci-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "minecraft-ci-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
minecraft-ci-releaseSet up and review CI, artifact publishing, versioning, and release management for Minecraft 26.x or legacy 1.21.x mods and Paper plugins.
Minecraft CI Release is an agent skill from Jahrome907/minecraft-agent-skills. Set up and review CI, artifact publishing, versioning, and release management for Minecraft 26.x or legacy 1.21.x mods and Paper plugins. Use for pipelines and releases, not gameplay implementation or server operations.
Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/publishing-gradle.md` and `scripts/validate-workflow-snippets.sh`).
It sits in Development, covering Open source maintenance. It works with GitHub, GitHub Actions, Java and Gradle. The repository describes itself as: Minecraft AI agent skills and dual-target plugin bundle for Codex and Claude Code. The licence is MIT.
Read from SKILL.md and the folder at commit dd57c5a. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 3 files in scripts/ (Shell and JavaScript), which the agent can run.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
docs.github.comgithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
MODRINTH_TOKENCURSEFORGE_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Minecraft CI Release loads about 3.6k tokens when it runs, and up to ~5k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 688 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from Jahrome907/minecraft-agent-skills at commit dd57c5a, republished under its MIT licence (© Jahrome907). 688 words, ~3,627 tokens.
.claude/skills/minecraft-ci-release/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.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).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-09-04; refresh them from the upstream tag before intentionally upgrading an action:
actions/checkout@v7.0.1 3d3c42e5aac5ba805825da76410c181273ba90b1
actions/setup-java@v6.0.0 dd06d9cba3e5552c54d9f8ea23572deb30010f7c
gradle/actions/setup-gradle@v6.3.0 9c971963bec38e04b3d30dcc455b5382be2fdbfb
actions/upload-artifact@v7.0.1 043fb46d1a93c77aae656e7c1c64a875d1fc6a0a
softprops/action-gh-release@v3.0.3 efb35369e0ad2afab669f228072c1b0d510eae64Minecraft mod versions follow: {mod_version}+{mc_version}
1.0.0+26.2 ← mod 1.0.0 for MC 26.2
1.2.3+26.2
2.0.0+26.2Use 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.2
tag: v1.2.3The 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.
This is a Minecraft 26.x / Java 25 example. Its displayed check names are
Build / Build (fabric), Build / Build (neoforge), and Build / Test after
the test job below is added. After the first successful pull request, copy the
exact names GitHub displays into branch protection; workflow or job renames
change the required-check context.
.github/workflows/build.ymlname: Build
on:
push:
branches: ["main", "develop"]
pull_request:
branches: ["main"]
permissions:
contents: read
jobs:
build:
name: Build (${{ matrix.platform }})
runs-on: ubuntu-latest
strategy:
matrix:
platform: [neoforge, fabric]
fail-fast: false
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1
- name: Set up Java 25
uses: actions/setup-java@dd06d9cba3e5552c54d9f8ea23572deb30010f7c
with:
java-version: "25"
distribution: "temurin"
- name: Setup Gradle
uses: gradle/actions/setup-gradle@9c971963bec38e04b3d30dcc455b5382be2fdbfb
with:
cache-read-only: ${{ github.event_name == 'pull_request' }}
- name: Grant execute permission for gradlew
run: chmod +x gradlew
- name: Build (${{ matrix.platform }})
run: ./gradlew :${{ matrix.platform }}:build --no-daemon
- name: Upload artifacts
uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a
with:
name: mod-${{ matrix.platform }}-${{ github.sha }}
path: ${{ matrix.platform }}/build/libs/*.jar
if-no-files-found: error
test:
name: Test
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1
- name: Set up Java 25
uses: actions/setup-java@dd06d9cba3e5552c54d9f8ea23572deb30010f7c
with:
distribution: temurin
java-version: "25"
- name: Set up Gradle
uses: gradle/actions/setup-gradle@9c971963bec38e04b3d30dcc455b5382be2fdbfb
- name: Run tests
run: ./gradlew test --no-daemon.github/workflows/release.ymlname: Release
on:
push:
tags:
- "v*"
permissions:
contents: write # for creating GitHub releases
jobs:
release:
name: Release
runs-on: ubuntu-latest
steps:
- name: Checkout tagged source
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1
- name: Set up Java 25
uses: actions/setup-java@dd06d9cba3e5552c54d9f8ea23572deb30010f7c
with:
java-version: "25"
distribution: "temurin"
- name: Setup Gradle
uses: gradle/actions/setup-gradle@9c971963bec38e04b3d30dcc455b5382be2fdbfb
- name: Grant execute permission for gradlew
run: chmod +x gradlew
- name: Validate tag and build
env:
MOD_VERSION: ${{ github.ref_name }}
run: |
MOD_VERSION="${MOD_VERSION#v}"
./gradlew verifyReleaseVersion build --no-daemon \
-PreleaseModVersion="$MOD_VERSION"
- name: Select release artifacts
env:
RELEASE_TAG: ${{ github.ref_name }}
run: |
mkdir -p release-artifacts
shopt -s nullglob
select_primary() {
local loader="$1"; shift
local matches=( "$@" )
if (( ${#matches[@]} != 1 )); then
printf 'Expected one %s primary JAR, found %s: %s\n' \
"$loader" "${#matches[@]}" "${matches[*]:-none}" >&2
exit 1
fi
cp "${matches[0]}" "release-artifacts/${loader}-${RELEASE_TAG}.jar"
}
select_primary fabric fabric/build/libs/*-fabric.jar
select_primary neoforge neoforge/build/libs/*-neoforge.jar
- name: Create GitHub Release
uses: softprops/action-gh-release@efb35369e0ad2afab669f228072c1b0d510eae64
with:
files: |
release-artifacts/fabric-${{ github.ref_name }}.jar
release-artifacts/neoforge-${{ github.ref_name }}.jar
fail_on_unmatched_files: true
generate_release_notes: true
prerelease: ${{ contains(github.ref_name, '-alpha') || contains(github.ref_name, '-beta') || contains(github.ref_name, '-rc') }}This workflow creates a GitHub Release only. It expects one primary Fabric JAR and one primary NeoForge JAR with loader-distinct names. Configure those classifiers in the project build, then change both patterns together if its naming convention differs. The selection step fails for zero or multiple matches and copies to distinct release names, preventing accidental overwrite or a partial release. Add a project-specific publisher after version validation only when that destination is in scope.
.github/workflows/build.yml (plugin)name: Build
on:
push:
branches: ["main"]
pull_request:
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1
- uses: actions/setup-java@dd06d9cba3e5552c54d9f8ea23572deb30010f7c
with:
java-version: "25"
distribution: "temurin"
- uses: gradle/actions/setup-gradle@9c971963bec38e04b3d30dcc455b5382be2fdbfb
- run: chmod +x gradlew
- run: ./gradlew build --no-daemon
- uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a
with:
name: plugin-${{ github.sha }}
path: build/libs/*.jar
if-no-files-found: error
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1
- uses: actions/setup-java@dd06d9cba3e5552c54d9f8ea23572deb30010f7c
with:
java-version: "25"
distribution: "temurin"
- uses: gradle/actions/setup-gradle@9c971963bec38e04b3d30dcc455b5382be2fdbfb
- run: ./gradlew test --no-daemonRead the publishing reference only when the
project publishes to Modrinth or CurseForge. It includes current plugin versions,
26.x jar selection, explicit legacy Loom remapJar guidance, version verification,
and a parser that fails when the expected changelog heading is missing.
gradle.properties Secrets PatternNever hardcode tokens. Read them from environment:
# gradle.properties (committed)
mod_id=mymod
mod_version=1.0.0
minecraft_version=26.2
modrinth_project_id=AABBCCDD
curseforge_project_id=123456
# DO NOT commit tokens
# Set these as GitHub repo secrets:
# MODRINTH_TOKEN, CURSEFORGE_TOKEN| Change | Version bump |
|---|---|
| New features, no breaking changes | Minor: 1.1.0 |
| Bug fixes only | Patch: 1.0.1 |
| API/config breaking changes | Major: 2.0.0 |
| Minecraft version update | Keep mod version, change the +26.2 suffix |
| Pre-release | 1.0.0-beta.1, 1.0.0-rc.1 |
# Changelog
## [1.1.0] — 2025-06-01
### Added
- New `/kit` command
- PDC-based kill tracker
### Fixed
- Death message not appearing on Paper 26.2
## [1.0.0] — 2025-05-01
### Added
- Initial releaseThe publishing reference extracts this section by mod_version and fails clearly
when the expected heading is missing.
.github/dependabot.ymlversion: 2
updates:
- package-ecosystem: "gradle"
directory: "/"
schedule:
interval: "weekly"
groups:
gradle-plugins:
patterns:
- "com.gradleup.shadow"
- "dev.architectury.loom"
- "com.modrinth.minotaur"
- "net.darkhax.curseforgegradle"
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "weekly"# In all workflow jobs:
- name: Setup Gradle
uses: gradle/actions/setup-gradle@9c971963bec38e04b3d30dcc455b5382be2fdbfb
with:
# Read-only cache on PRs, read-write on main
cache-read-only: ${{ github.event_name == 'pull_request' }}Recommended GitHub branch protection for main:
Build / Build (fabric), Build / Build (neoforge), and Build / Test#!/usr/bin/env bash
# scripts/release.sh <mod-version>
set -euo pipefail
VERSION="${1:?Usage: release.sh <mod-version>}"
REMOTE="${RELEASE_REMOTE:-origin}"
BRANCH="${RELEASE_BRANCH:-main}"
EXPECTED_REMOTE_URL="${RELEASE_REMOTE_URL:?Set RELEASE_REMOTE_URL to the expected push URL}"
git diff --check
[[ -z "$(git status --porcelain=v1 --untracked-files=all)" ]] \
|| { echo "Working tree contains staged, unstaged, or untracked files." >&2; exit 1; }
[[ "$(git branch --show-current)" == "$BRANCH" ]] \
|| { echo "Release must start from branch $BRANCH." >&2; exit 1; }
mapfile -t PUSH_URLS < <(git remote get-url --push --all "$REMOTE")
[[ ${#PUSH_URLS[@]} -eq 1 && "${PUSH_URLS[0]}" == "$EXPECTED_REMOTE_URL" ]] \
|| { echo "Remote $REMOTE must have one expected push URL." >&2; exit 1; }
! git rev-parse --verify --quiet "refs/tags/v${VERSION}" >/dev/null \
|| { echo "Local tag v${VERSION} already exists." >&2; exit 1; }
set +e
git ls-remote --exit-code --tags "$EXPECTED_REMOTE_URL" "refs/tags/v${VERSION}" >/dev/null
REMOTE_TAG_STATUS=$?
set -e
case "$REMOTE_TAG_STATUS" in
0) echo "Remote tag v${VERSION} already exists." >&2; exit 1 ;;
2) ;;
*) echo "Could not verify remote tag v${VERSION}." >&2; exit "$REMOTE_TAG_STATUS" ;;
esac
./gradlew verifyReleaseVersion --no-daemon -PreleaseModVersion="$VERSION"
git tag --annotate "v${VERSION}" --message "Release v${VERSION}"
git push "$REMOTE" "HEAD:refs/heads/${BRANCH}"
git push "$REMOTE" "refs/tags/v${VERSION}"Update and verify version/changelog files before this script, then tag that release
commit. Set RELEASE_BRANCH, RELEASE_REMOTE, and RELEASE_REMOTE_URL for the
intended release branch and exact push URL. Do not force-push or retag a published
release without explicit authorization.
Run the bundled validator from an installed minecraft-ci-release skill directory:
# Run from the installed skill directory:
./scripts/validate-workflow-snippets.sh --root .
# Strict mode treats warnings as failures:
./scripts/validate-workflow-snippets.sh --root . --strictThe validator is bundled and self-contained. Run it from a copied .agents/,
.codex/, or .claude/ minecraft-ci-release skill directory without relying
on repo-root node_modules.
It validates workflow-shaped YAML, unresolved placeholders, workflow secret
documentation, and remote uses: references pinned to full commit SHAs. Local
actions (./...) and Docker actions (docker://...) are intentionally excluded from
the SHA requirement. It reads only this skill's SKILL.md: it does not validate a
project's .github/workflows files or Gradle tasks. Before a real release, inspect
the project's generated artifacts, run verifyReleaseVersion, and review the exact
workflow diff and configured release destination.
© Jahrome907, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (scripts, references) in .codex/skills/minecraft-ci-release of Jahrome907/minecraft-agent-skills.
Open the folder on GitHubat commit dd57c5a
Minecraft CI Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Minecraft CI Release this skillJahrome907/minecraft-agent-skills | 170 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Releasesol4k/sol4k | 135 | — | ~949 | Automated safety check: Pass | Apache-2.0 | |
| Git Init Remoteexception-coder/npe_get_jobs | 176 | — | ~662 | Automated safety check: Pass | Custom licence | |
| Dependabot PR Reviewkernitus/BukkitOldCombatMechanics | 225 | — | ~882 | Automated safety check: Pass | MPL-2.0 | |
| GitHub Issue Triagedecebals/claude-code-java | 751 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dependabotgithub/awesome-copilot | 40k | 1 repos | ~3.4k | Automated safety check: Pass | MIT |
sol4k/sol4k
Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.
exception-coder/npe_get_jobs
Initialize git in a local project without a repository, connect it to a remote, and generate a proper .gitignore.
kernitus/BukkitOldCombatMechanics
A skill your agent uses for Dependabot PRs, dependency bumps, Gradle or Maven dependency updates, GitHub Actions updates, dependency changelog/licence/release-note review, JVM/classfile checks, and…
decebals/claude-code-java
Sorts open GitHub issues for a Java project into bug, feature, question, duplicate or unclear, then labels them and assigns a priority.
github/awesome-copilot
Comprehensive guide for configuring and managing GitHub Dependabot.
Community-Access/accessibility-agents
Scaffold a repo: templates, contributing guides, CI, labels, licenses.
Jahrome907/minecraft-agent-skills
Write and debug Minecraft Java 26.x and 1.21.x commands, selectors, execute chains, scoreboards, NBT, and RCON scripts.
Jahrome907/minecraft-agent-skills
Create, edit, and debug vanilla Minecraft 26.x and 1.21.x datapacks, including functions, advancements, recipes, loot tables, predicates, tags, and pack metadata.
Jahrome907/minecraft-agent-skills
Create, modify, debug, or migrate Minecraft mods for current NeoForge or Fabric 26.x, legacy 1.21.x, and Forge 1.20.1.
Jahrome907/minecraft-agent-skills
Create, modify, and debug server plugins for current Paper 26.x on Java 25 or legacy Bukkit-derived 1.21.x servers on Java 21.
Jahrome907/minecraft-agent-skills
Create and debug Minecraft 26.x and 1.21.x resource packs, including pack metadata, textures, models, blockstates, item definitions, sounds, fonts, animations, and shaders.
Jahrome907/minecraft-agent-skills
Design and implement automated tests for current Minecraft 26.x or legacy 1.21.x mods and plugins using JUnit, MockBukkit, NeoForge Game Tests, or Fabric Game Tests.
Works with
Categories
Set up and review CI, artifact publishing, versioning, and release management for Minecraft 26.x or legacy 1.21.x mods and Paper plugins. Minecraft CI Release is an agent skill from Jahrome907/minecraft-agent-skills.x mods and Paper plugins.
Minecraft CI Release fits situations like: pipelines and releases; not gameplay implementation; server operations.
Run `npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-ci-release -a claude-code`. Or copy the skill folder (.codex/skills/minecraft-ci-release in Jahrome907/minecraft-agent-skills) into .claude/skills/minecraft-ci-release in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-ci-release -a codex`. Or copy the skill folder (.codex/skills/minecraft-ci-release in Jahrome907/minecraft-agent-skills) into .agents/skills/minecraft-ci-release in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-ci-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/minecraft-ci-release, .gemini/skills/minecraft-ci-release, .github/skills/minecraft-ci-release and .opencode/skills/minecraft-ci-release in your project.
Going by SKILL.md and its folder, Minecraft CI Release needs a shell and JavaScript for the scripts in its folder, the command-line tools its instructions call (git) and credentials named MODRINTH_TOKEN and CURSEFORGE_TOKEN. Our summary lists: Node.js; A Bash shell; A credential in MODRINTH_TOKEN; A credential in CURSEFORGE_TOKEN.
SKILL.md names 2 domains. As links in the text: docs.github.com and github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Minecraft CI Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.6k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Minecraft CI Release: Release (sol4k/sol4k, 135 stars), Git Init Remote (exception-coder/npe_get_jobs, 176 stars), Dependabot PR Review (kernitus/BukkitOldCombatMechanics, 225 stars) and GitHub Issue Triage (decebals/claude-code-java, 751 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Jahrome907 (a GitHub user) maintains it in Jahrome907/minecraft-agent-skills, which has 170 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 13, 2026.
Source: Jahrome907/minecraft-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.