How do I install the Junit5 CI skill?

Run npx skillmds@latest add jovd83/junit5-ci in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Junit5 CI safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Junit5 CI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Junit5 CI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Junit5 CI?

jovd83 (@jovd83) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Junit5 CI by jovd83 — Agent Skill

Name: Junit5 CI
Author: jovd83

File contents

JUnit 5 CI

1. Inspect the Execution Path

Identify whether the repo uses Maven, Gradle, the Console Launcher, or mixed execution paths.
Confirm how tests are filtered, tagged, and reported.
Read references/build-and-run.md before changing pipeline behavior.
Read references/tool-recipes.md when the repo supports more than one execution path.

2. Configure Safely

Use useJUnitPlatform() in Gradle-based execution.
Use current Surefire or Failsafe configuration already established by the repo when possible.
Keep tags, includes, excludes, and reporting explicit.
Use junit-platform.properties for shared execution parameters when the repo already follows that pattern.
Keep local and CI commands aligned unless the repo intentionally separates them.

3. Debug CI Failures

Compare local and CI Java versions.
Compare environment variables, locale, time zone, and file-system assumptions.
Compare build commands and active profiles.
Read references/ci-failure-patterns.md when failures reproduce only in automation.
Read references/tagging-and-reporting.md before changing tag filters or report outputs.

4. Examples

Input: Make these JUnit 5 integration tests run in Maven CI only. Output: Configure naming, tags, or Failsafe boundaries without breaking fast local feedback.
Input: Gradle discovers no tests. Output: Verify useJUnitPlatform(), naming conventions, and source-set wiring.
Input: Split fast unit tests from slower integration coverage in Maven. Output: Use tags, naming, or Surefire/Failsafe boundaries that fit the existing build model.

5. Troubleshooting

Problem: No tests are discovered. Fix: Check task configuration, naming conventions, and JUnit Platform enablement.
Problem: CI fails but local passes. Fix: Compare Java version, environment, and execution flags before changing test logic.
Problem: Reports exist locally but not in CI artifacts. Fix: Check report output paths, pipeline artifact collection, and the actual test task that runs in automation.

---name: junit5-cidescription: Use when Codex needs to run JUnit 5 tests through Maven, Gradle, or the Console Launcher, configure CI pipelines, manage tags and reports, or debug environment-specific execution issues.---# JUnit 5 CI## 1. Inspect the Execution Path1. Identify whether the repo uses Maven, Gradle, the Console Launcher, or mixed execution paths.2. Confirm how tests are filtered, tagged, and reported.3. Read [references/build-and-run.md](references/build-and-run.md) before changing pipeline behavior.4. Read [references/tool-recipes.md](references/tool-recipes.md) when the repo supports more than one execution path.## 2. Configure Safely1. Use `useJUnitPlatform()` in Gradle-based execution.2. Use current Surefire or Failsafe configuration already established by the repo when possible.3. Keep tags, includes, excludes, and reporting explicit.4. Use `junit-platform.properties` for shared execution parameters when the repo already follows that pattern.5. Keep local and CI commands aligned unless the repo intentionally separates them.## 3. Debug CI Failures1. Compare local and CI Java versions.2. Compare environment variables, locale, time zone, and file-system assumptions.3. Compare build commands and active profiles.4. Read [references/ci-failure-patterns.md](references/ci-failure-patterns.md) when failures reproduce only in automation.5. Read [references/tagging-and-reporting.md](references/tagging-and-reporting.md) before changing tag filters or report outputs.## 4. Examples1. Input: `Make these JUnit 5 integration tests run in Maven CI only.` Output: Configure naming, tags, or Failsafe boundaries without breaking fast local feedback.2. Input: `Gradle discovers no tests.` Output: Verify `useJUnitPlatform()`, naming conventions, and source-set wiring.3. Input: `Split fast unit tests from slower integration coverage in Maven.` Output: Use tags, naming, or Surefire/Failsafe boundaries that fit the existing build model.## 5. Troubleshooting1. Problem: No tests are discovered. Fix: Check task configuration, naming conventions, and JUnit Platform enablement.2. Problem: CI fails but local passes. Fix: Compare Java version, environment, and execution flags before changing test logic.3. Problem: Reports exist locally but not in CI artifacts. Fix: Check report output paths, pipeline artifact collection, and the actual test task that runs in automation.

Frequently asked questions

Junit5 CI