Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

junit5-installer-vscode-codex

Estrelas0

Forks0

Atualizado13 de maio de 2026 às 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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

jovd83

jovd83/junit5-skill

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·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.

Mais deste repositório

mesmo repositório

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.