Run any Skill in Manus with one click

junit5-installer-vscode-codex

Stars0

Forks0

UpdatedMay 13, 2026 at 06:22

Use when Codex needs to help configure Visual Studio Code for JUnit 5 development, execution, debugging, and Codex-driven workflows in a JVM project.

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

jovd83

jovd83/junit5-skill

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	junit5-installer-vscode-codex
description	Use when Codex needs to help configure Visual Studio Code for JUnit 5 development, execution, debugging, and Codex-driven workflows in a JVM project.
metadata	{"author":"jovd83","version":"1.0.0","dispatcher-category":"testing","dispatcher-capabilities":"editor-setup, junit5-editor-setup","dispatcher-accepted-intents":"setup_junit_editor","dispatcher-input-artifacts":"editor_choice, repo_context, local_environment","dispatcher-output-artifacts":"editor_setup_steps, configuration_guidance","dispatcher-stack-tags":"junit5, setup, editor","dispatcher-risk":"low","dispatcher-writes-files":false}

JUnit 5 VS Code Setup

1. Confirm the Project Shape

Confirm the repo uses Maven or Gradle.
Confirm the expected JDK version.
Confirm test dependencies resolve successfully.

2. Configure the Workspace

Open the repo root, not a detached subfolder.
Ensure Java tooling and test execution extensions are active.
Let the build tool remain the source of truth for classpath and runner behavior.

3. Validate

Run one focused test class.
Debug one test method.
Confirm terminal execution matches IDE execution.

More from this repository

same repository

junit5-skill

jovd83/junit5-skill

Use when Codex needs to create, run, evaluate, debug, correct, modernize, document, or route JUnit 5 tests and related workflows across component, integration, slice, repository, service, regression, smoke, and migration scenarios.

2026-05-130

junit5-analysis

jovd83/junit5-skill

Use when Codex needs to derive JUnit 5 test scenarios from requirements, code, or existing test case definitions such as TDD, BDD, and plain-text specifications.

2026-05-130

junit5-architecture

jovd83/junit5-skill

Use when Codex needs to shape or refactor JUnit 5 suite architecture, test package structure, naming, fixture ownership, reuse patterns, or boundaries between component, integration, and service tests.

2026-05-130

junit5-ci

jovd83/junit5-skill

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.

2026-05-130

junit5-core

jovd83/junit5-skill

Use when Codex needs to create, run, debug, evaluate, refactor, or correct JUnit 5 tests across component, integration, slice, repository, service, smoke, or regression scenarios.

2026-05-130

junit5-documentation-root-cause

jovd83/junit5-skill

Use when Codex needs to analyze a failing JUnit 5 test run, identify the most likely root cause, and produce a developer-focused diagnosis with concrete next fixes.

2026-05-130

name	junit5-installer-vscode-codex
description	Use when Codex needs to help configure Visual Studio Code for JUnit 5 development, execution, debugging, and Codex-driven workflows in a JVM project.
metadata	{"author":"jovd83","version":"1.0.0","dispatcher-category":"testing","dispatcher-capabilities":"editor-setup, junit5-editor-setup","dispatcher-accepted-intents":"setup_junit_editor","dispatcher-input-artifacts":"editor_choice, repo_context, local_environment","dispatcher-output-artifacts":"editor_setup_steps, configuration_guidance","dispatcher-stack-tags":"junit5, setup, editor","dispatcher-risk":"low","dispatcher-writes-files":false}

JUnit 5 VS Code Setup

1. Confirm the Project Shape

Confirm the repo uses Maven or Gradle.
Confirm the expected JDK version.
Confirm test dependencies resolve successfully.

2. Configure the Workspace

Open the repo root, not a detached subfolder.
Ensure Java tooling and test execution extensions are active.
Let the build tool remain the source of truth for classpath and runner behavior.

3. Validate

Run one focused test class.
Debug one test method.
Confirm terminal execution matches IDE execution.