New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Integration Test Verification

by kernitus in kernitus/BukkitOldCombatMechanics

A skill your agent uses 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…

MPL-2.0Auto-check passedTesting & QA

Install Integration Test Verification

skills CLI
$ npx skills add kernitus/BukkitOldCombatMechanics --skill integration-test-verification -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kernitus/BukkitOldCombatMechanics integration-test-verification --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/integration-test-verification .claude/skills/integration-test-verification && rm -rf skills-src

Use ~/.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/

Facts

Skill name
integration-test-verification
GitHub stars
225
Token cost
~1.2k tokens
SKILL.md length
476 words
Files
2 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
MPL-2.0

At a glance

A skill your agent uses 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…

  • Works in 5 steps: Identify the changed feature and… → Prefer the narrowest version set that… → If the change touches packet handling,… → …
  • Triaging integration tests
  • SKILL.md covers When to use, When not to use, Non-negotiable rules and Harness quick reference, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Integration Test Verification is an agent skill from kernitus/BukkitOldCombatMechanics. 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.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/relocated-agents-notes.md`).

It sits in Testing & QA, covering Integration testing and Test generation. It works with Gradle. The repository describes itself as: Minecraft plugin to configure combat mechanics for 1.9 onwards. The licence is MPL-2.0.

When your agent uses it

  • Triaging integration tests
  • Gradle matrix tasks
  • FakePlayer-backed test cases
  • Compact test-result files

Example prompts

  • “/integration-test-verification”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identify the changed feature and affected server bands.
  2. Prefer the narrowest version set that covers the compatibility boundary.
  3. If the change touches packet handling, include a modern PacketEvents-covered version.
  4. If the change touches legacy behaviour or Java 8 APIs, include 1.12 where practical.
  5. If the change is documentation or opencode-only, run filesystem/schema checks rather than server tests.

What it can do on your machine

Read from SKILL.md and the folder at commit e66e7a9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Integration Test Verification loads about 1.2k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 71 tokens; SKILL.md has 476 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

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.

Safety

Auto-check passed

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from kernitus/BukkitOldCombatMechanics at commit e66e7a9, republished under its MPL-2.0 licence (© kernitus). 476 words, ~1,249 tokens.

Download SKILL.mdSave it as .claude/skills/integration-test-verification/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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.

Integration Test Verification

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.

When to use

  • Selecting ./gradlew integrationTest versus a version-limited matrix run.
  • Adding or changing Kotlin integration tests under src/integrationTest/kotlin.
  • Registering a new spec in KotestRunner.
  • Triaging checkTestResults<version> output or plugins/OldCombatMechanicsTest/test-failures.txt.
  • Reasoning about tests that use FakePlayer, synthetic Bukkit events, PacketEvents wrappers, or direct module handler calls.

When not to use

  • Do not use for release asset, Hangar, CurseForge, or licence checks; use release-readiness-review.
  • Do not use for module assignment or config migration design unless the task is specifically about test coverage; use module-config-change.
  • Do not use for broad Java 8/NMS design unless the immediate question is test-harness behaviour; use compatibility-strategy.

Non-negotiable rules

  • Root and user-facing agents must not read 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.
  • Prefer compact console output and plugins/OldCombatMechanicsTest/test-failures.txt first for failure triage.
  • Do not disable, skip, weaken, or version-gate tests as a way to make validation pass. Fix the root cause, or report the failure as a blocker unless the user explicitly approves a coverage reduction.
  • New integration specs must be added to KotestRunner.withClasses(...); autoscan is disabled.
  • Keep paths relative to the repository root, plugin data folder, or server run directory.
  • Avoid starting servers for documentation-only or opencode-config-only changes.
Show full SKILL.md (243 more words)Show less

Harness quick reference

  • Full matrix: ./gradlew integrationTest.
  • Selected matrix: ./gradlew integrationTest -PintegrationTestVersions=1.19.2,1.21.11,1.12.
  • Wrapper helper: scripts/run-integration-matrix.sh -v 1.19.2,1.21.11 [-s '*SpecName*'] [-t '*test name*'] keeps Gradle and Kotest filter arguments consistent.
  • Compact result summary: scripts/summarise-integration-results.sh reads only run/*/plugins/OldCombatMechanicsTest/test-results.txt and test-failures.txt; it does not open full server logs.
  • Matrix suggestion helper: scripts/suggest-integration-matrix.sh [changed-path ...] gives a conservative starting point for versions and filters.
  • Individual task names follow integrationTest<version> with punctuation mapped to underscores, for example integrationTest1_19_2.
  • Test plugin entrypoint: kernitus.plugin.OldCombatMechanics.OCMTestMain.
  • Success handoff: plugins/OldCombatMechanicsTest/test-results.txt contains PASS.
  • Failure summary: plugins/OldCombatMechanicsTest/test-failures.txt contains a compact list, capped for CI readability.
  • Java 11+ server targets use Kotest 6 (KotestRunner, KotestProjectConfig).
  • Java 8 targets use LegacyTestRunner, currently only a smoke path.

Validation selection template

  1. Identify the changed feature and affected server bands.
  2. Prefer the narrowest version set that covers the compatibility boundary.
  3. If the change touches packet handling, include a modern PacketEvents-covered version.
  4. If the change touches legacy behaviour or Java 8 APIs, include 1.12 where practical.
  5. If the change is documentation or opencode-only, run filesystem/schema checks rather than server tests.

Example recommendation:

text
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.

Known shortcut patterns

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.
  • Packet cancellation tests construct and dispatch PacketEvents events directly for deterministic coverage.

Treat these shortcuts as design choices unless the task asks for end-to-end realism.

References

  • Historical integration and regression notes: references/relocated-agents-notes.md.

© kernitus, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/integration-test-verification of kernitus/BukkitOldCombatMechanics.

  • SKILL.md
  • references/relocated-agents-notes.md

Open the folder on GitHubat commit e66e7a9

Compare with similar skills

Integration Test Verification 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.

Integration Test Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Integration Test Verification this skillkernitus/BukkitOldCombatMechanics225—~1.2kAutomated safety check: PassMPL-2.0
OpenROAD Module Test AdderThe-OpenROAD-Project/OpenROAD3.2k—~1.8kAutomated safety check: PassBSD-3-Clause
Syncable Entity Integration Teststwentyhq/twenty58k—~3.4kAutomated safety check: PassCustom licence
Con CLI E2Enowledge-co/con-terminal625—~1.2kAutomated safety check: PassMIT
Write Testsgrafana/synthetic-monitoring-app171—~1.2kAutomated safety check: PassAGPL-3.0
Write Test389ds/389-ds-base294—~1.8kAutomated safety check: PassCustom licence

Similar skills

  • OpenROAD Module Test Adder

    The-OpenROAD-Project/OpenROAD

    Adds integration or unit tests to an OpenROAD module: writes the Tcl test, generates golden files and registers it in both CMake and Bazel.

    3.2k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

  • Syncable Entity Integration Tests

    twentyhq/twenty

    Step-by-step guide to writing the mandatory integration tests for syncable metadata entities in Twenty's server, covering failures and CRUD success cases.

    58k GitHub stars~3.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Con CLI E2E

    nowledge-co/con-terminal

    Validate Con's local socket control plane against a real running app session, and write/run con-test integration tests.

    625 GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Write Tests

    grafana/synthetic-monitoring-app

    Official

    Write Jest integration and unit tests for the Grafana Synthetic Monitoring app using React Testing Library, MSW, and src/test helpers.

    171 GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Write Test

    389ds/389-ds-base

    Add or extend a pytest integration test for 389 Directory Server under dirsrvtests/.

    294 GitHub stars~1.8k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Grails Test Fixer

    apache/grails-core

    Guides running, reviewing and fixing test failures across grails-core modules with Gradle, including targeted runs and the aggregate HTML and Markdown reports.

    2.9k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed

More from kernitus/BukkitOldCombatMechanics

All 9 skills in this repo

  • Dependabot PR Review

    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…

    225 GitHub stars~882 tokensUpdated 4 days ago
    Auto-check passed

  • Module Config Change

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses for config.yml, module enablement, modesets, config migration, configurable module assignment, and per-module option changes; do not use for unrelated integration-test…

    225 GitHub stars~914 tokensUpdated 4 days ago
    Auto-check passed

  • PR Draft Summary

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses when drafting pull-request titles, descriptions, change summaries, risk notes, validation sections, or reviewer handoff text; do not use for implementation design, release…

    225 GitHub stars~526 tokensUpdated 4 days ago
    Auto-check passed

  • Release Readiness Review

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for…

    225 GitHub stars~1.5k tokensUpdated 4 days ago
    Auto-check passed

  • User Facing Changelog

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses 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…

    225 GitHub stars~1.3k tokensUpdated 4 days ago
    Auto-check passed

  • Compatibility Strategy

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses for Java 8 backports, Bukkit/Paper version differences, NMS/reflection, PacketEvents compatibility, fake-player implementation choices, and feature-detection design; do not…

    225 GitHub stars~824 tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Integration Test Verification

What does Integration Test Verification do?

A skill your agent uses 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…. Integration Test Verification is an agent skill from kernitus/BukkitOldCombatMechanics. 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.

When should I use Integration Test Verification?

Integration Test Verification fits situations like: triaging integration tests; gradle matrix tasks; fakePlayer-backed test cases; compact test-result files.

How do I install Integration Test Verification in Claude Code?

Run `npx skills add kernitus/BukkitOldCombatMechanics --skill integration-test-verification -a claude-code`. Or copy the skill folder (.agents/skills/integration-test-verification in kernitus/BukkitOldCombatMechanics) into .claude/skills/integration-test-verification in your project. Claude Code loads it when a task matches its description.

How do I install Integration Test Verification in Codex?

Run `npx skills add kernitus/BukkitOldCombatMechanics --skill integration-test-verification -a codex`. Or copy the skill folder (.agents/skills/integration-test-verification in kernitus/BukkitOldCombatMechanics) into .agents/skills/integration-test-verification in your project. Codex loads it when a task matches its description.

Can I use Integration Test Verification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kernitus/BukkitOldCombatMechanics --skill integration-test-verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/integration-test-verification, .gemini/skills/integration-test-verification, .github/skills/integration-test-verification and .opencode/skills/integration-test-verification in your project.

What does Integration Test Verification need to run?

SKILL.md names no scripts, command-line tools or credentials: Integration Test Verification is instructions for the agent only.

Does Integration Test Verification access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Integration Test Verification safe to install?

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. Review the folder before installing.

What licence does Integration Test Verification use?

Integration Test Verification is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Integration Test Verification use?

About 1.2k tokens (SKILL.md is roughly 5k 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 2.3k tokens, read only when the agent opens those files.

What are the alternatives to Integration Test Verification?

Skills that share tags, products or a category with Integration Test Verification: OpenROAD Module Test Adder (The-OpenROAD-Project/OpenROAD, 3.2k stars), Syncable Entity Integration Tests (twentyhq/twenty, 58k stars), Con CLI E2E (nowledge-co/con-terminal, 625 stars) and Write Tests (grafana/synthetic-monitoring-app, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Integration Test Verification?

kernitus (a GitHub user) maintains it in kernitus/BukkitOldCombatMechanics, which has 225 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 4, 2026.

Source: kernitus/BukkitOldCombatMechanics on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.