java-test-rules
Apply SHAFT Java test lifecycle, parallelism, isolation, Allure, browser, and regression rules when editing src/test Java files.
git clone --depth 1 https://github.com/ShaftHQ/SHAFT_ENGINE /tmp/java-test-rules && cp -r /tmp/java-test-rules/.agents/skills/java-test-rules ~/.claude/skills/java-test-rulesSKILL.md
# Java Test Rules Read and follow the [canonical Java test rules](../../../.github/instructions/java-tests.instructions.md). Load them only when test Java is in scope.
Investigate GitHub Actions and SHAFT Allure failures from a run, PR, or job; separate code defects from infrastructure and provider failures.
Diagnose and stabilize intermittent SHAFT tests, especially TestNG parallelism, shared state, files, drivers, timing, and external dependencies.
Apply SHAFT production Java compatibility, API, properties, logging, Allure, and WebDriver rules when editing src/main Java files.
Prepare or review a SHAFT release by checking reactor versions, metadata, examples, consumer fixtures, stable dependency updates, and Maven Central publication safeguards.
Archived historical SHAFT_ENGINE Gemma integration retained outside active skill discovery.