// Use when running, selecting, authoring, or triaging integration tests, Kotest specs, Gradle matrix tasks, FakePlayer-backed test cases, or compact test-result files; do not use for unrelated production-only edits, release publishing, or general PR prose.
Use when rewriting CHANGELOG.md, GitHub release notes, or Release Please PR changelog sections into user-facing release notes; do not use for release publishing, assets, licence, or workflow readiness checks.
Supports preparing commits, pre-commit hooks, Spotless, formatting or linting, validation before commit, staging files, and writing conventional commits.
Use for GitHub issue triage and local investigation, including gh issue workflows, picking a fresh issue, reproducing issue reports, and planning regression coverage.
Use for Dependabot PRs, dependency bumps, Gradle or Maven dependency updates, GitHub Actions updates, dependency changelog/licence/release-note review, JVM/classfile checks, and validation recommendations.
Use for Java 8 backports, Bukkit/Paper version differences, NMS/reflection, PacketEvents compatibility, fake-player implementation choices, and feature-detection design; do not use for release publishing, PR wording, or simple test-running decisions.
Use for config.yml, module enablement, modesets, config migration, configurable module assignment, and per-module option changes; do not use for unrelated integration-test triage, release publishing, or PR summaries.
| name | integration-test-verification |
| description | Use when running, selecting, authoring, or triaging integration tests, Kotest specs, Gradle matrix tasks, FakePlayer-backed test cases, or compact test-result files; do not use for unrelated production-only edits, release publishing, or general PR prose. |
Use this skill for the repository's Paper-backed integration-test harness and for deciding how to validate a change without opening large server logs by default.
./gradlew integrationTest versus a version-limited matrix run.src/integrationTest/kotlin.KotestRunner.checkTestResults<version> output or plugins/OldCombatMechanicsTest/test-failures.txt.FakePlayer, synthetic Bukkit events, PacketEvents wrappers, or direct module handler calls.release-readiness-review.module-config-change.compatibility-strategy.build/integration-test-logs/*.log directly; log inspection is allowed only by subagents, and only when needed for integration-test triage or when explicitly requested.plugins/OldCombatMechanicsTest/test-failures.txt first for failure triage.KotestRunner.withClasses(...); autoscan is disabled../gradlew integrationTest../gradlew integrationTest -PintegrationTestVersions=1.19.2,1.21.11,1.12.scripts/run-integration-matrix.sh -v 1.19.2,1.21.11 [-s '*SpecName*'] [-t '*test name*'] keeps Gradle and Kotest filter arguments consistent.scripts/summarise-integration-results.sh reads only run/*/plugins/OldCombatMechanicsTest/test-results.txt and test-failures.txt; it does not open full server logs.scripts/suggest-integration-matrix.sh [changed-path ...] gives a conservative starting point for versions and filters.integrationTest<version> with punctuation mapped to underscores, for example integrationTest1_19_2.kernitus.plugin.OldCombatMechanics.OCMTestMain.plugins/OldCombatMechanicsTest/test-results.txt contains PASS.plugins/OldCombatMechanicsTest/test-failures.txt contains a compact list, capped for CI readability.KotestRunner, KotestProjectConfig).LegacyTestRunner, currently only a smoke path.1.12 where practical.Example recommendation:
Run: ./gradlew integrationTest -PintegrationTestVersions=1.19.2,1.21.11
Reason: covers modern Paper plus the PacketEvents path affected by the change.
Avoid: opening build/integration-test-logs from a root or user-facing agent; use a subagent only when compact failure output is insufficient or log inspection is explicitly requested.
Some tests intentionally exercise module code without fully realistic gameplay plumbing:
GoldenAppleIntegrationTest, OldPotionEffectsIntegrationTest, OldArmourDurabilityIntegrationTest, PlayerKnockbackIntegrationTest, SwordBlockingIntegrationTest, and SwordSweepIntegrationTest use synthetic events in places.PlayerKnockbackIntegrationTest and SwordSweepIntegrationTest directly invoke module handlers.Treat these shortcuts as design choices unless the task asks for end-to-end realism.
references/relocated-agents-notes.md.