Run any Skill in Manus with one click

minecraft-ping-network-release-gate

Stars0

Forks0

UpdatedApril 18, 2026 at 19:22

Use for networking, staging backend, release, packaging, workflow, or integration-harness changes in minecraft-ping. Adds the extra release-path and dual-stack validation gates.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

omkhar

omkhar/minecraft-ping

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	minecraft-ping-network-release-gate
description	Use for networking, staging backend, release, packaging, workflow, or integration-harness changes in minecraft-ping. Adds the extra release-path and dual-stack validation gates.

Minecraft Ping Network And Release Gate

Use this skill when a change touches Java or Bedrock networking, address resolution, the staging backend, release integration, packaging, or GitHub workflows.

Extra Invariants

The native staging backend and the container-backed path must keep matching the real release path.
Release docs, workflow behavior, and artifact-verification instructions must describe the same process.
Public release docs should assume a public GitHub repository and must not keep private-launch caveats.

Required Workflow

Run the normal change gate first.
Run make integration.
If the change affects packaging, archives, signing, provenance, SBOMs, or release automation, also run:
- goreleaser release --snapshot --clean --skip=sign
- make release-archive-smoke
- make release-repro
- make package-smoke ARCH=amd64
When touching workflow policy, keep README.md, docs/development.md, docs/releasing.md, and docs/release-verification.md aligned with the workflow files.
Prefer deleting internal-only release helpers over documenting them.

More from this repository

same repository

minecraft-ping-change-gate

omkhar/minecraft-ping

Use for every change in minecraft-ping. Enforces the repo's change gate: simplicity first, correctness, linting, appropriate tests, security, performance, idiomatic Go, dead-code cleanup, and public-repo hygiene.

2026-04-180

minecraft-ping-release-gate

omkhar/minecraft-ping

Use for release preparation, tag creation, and post-release verification in minecraft-ping. Enforces the public release checklist, Go-version recheck, and verification workflow.

2026-04-180

minecraft-ping-review-gate

omkhar/minecraft-ping

Use for code review in minecraft-ping. Enforces a findings-first review focused on correctness, regressions, test gaps, security, performance, simplicity, and public-repo hygiene.

2026-04-180

name	minecraft-ping-network-release-gate
description	Use for networking, staging backend, release, packaging, workflow, or integration-harness changes in minecraft-ping. Adds the extra release-path and dual-stack validation gates.

Minecraft Ping Network And Release Gate

Use this skill when a change touches Java or Bedrock networking, address resolution, the staging backend, release integration, packaging, or GitHub workflows.

Extra Invariants

The native staging backend and the container-backed path must keep matching the real release path.
Release docs, workflow behavior, and artifact-verification instructions must describe the same process.
Public release docs should assume a public GitHub repository and must not keep private-launch caveats.

Required Workflow

Run the normal change gate first.
Run make integration.
If the change affects packaging, archives, signing, provenance, SBOMs, or release automation, also run:
- goreleaser release --snapshot --clean --skip=sign
- make release-archive-smoke
- make release-repro
- make package-smoke ARCH=amd64
When touching workflow policy, keep README.md, docs/development.md, docs/releasing.md, and docs/release-verification.md aligned with the workflow files.
Prefer deleting internal-only release helpers over documenting them.