Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

junit5-reporting-stakeholder

Estrelas0

Forks0

Atualizado13 de maio de 2026 às 06:22

Use when Codex needs to summarize JUnit 5 test execution results for non-technical stakeholders in clear business-oriented language instead of raw runner output.

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

Especialistas em gestão de projetosNegócios e Operações Financeiras·SOC 13-1082

SKILL.md

readonly

name	junit5-reporting-stakeholder
description	Use when Codex needs to summarize JUnit 5 test execution results for non-technical stakeholders in clear business-oriented language instead of raw runner output.
metadata	{"author":"jovd83","version":"1.0.0","dispatcher-category":"testing","dispatcher-capabilities":"stakeholder-reporting, junit5-stakeholder-reporting","dispatcher-accepted-intents":"summarize_junit_results","dispatcher-input-artifacts":"execution_results, tested_scope, release_context","dispatcher-output-artifacts":"stakeholder_summary, release_health_report","dispatcher-stack-tags":"junit5, reporting, stakeholder","dispatcher-risk":"low","dispatcher-writes-files":false}

JUnit 5 Stakeholder Reporting

1. Collect the Outcome

Identify what ran, what passed, what failed, and what was skipped.
Identify whether the failures block release confidence or are isolated.

2. Translate into Stakeholder Language

Explain business impact, not stack traces.
Group failures by user-facing risk.
Call out confidence level and next action clearly.

3. Troubleshooting

Problem: The raw output is noisy. Fix: Collapse it into impacted capability, confidence, and next action.

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-reporting-stakeholder
description	Use when Codex needs to summarize JUnit 5 test execution results for non-technical stakeholders in clear business-oriented language instead of raw runner output.
metadata	{"author":"jovd83","version":"1.0.0","dispatcher-category":"testing","dispatcher-capabilities":"stakeholder-reporting, junit5-stakeholder-reporting","dispatcher-accepted-intents":"summarize_junit_results","dispatcher-input-artifacts":"execution_results, tested_scope, release_context","dispatcher-output-artifacts":"stakeholder_summary, release_health_report","dispatcher-stack-tags":"junit5, reporting, stakeholder","dispatcher-risk":"low","dispatcher-writes-files":false}

JUnit 5 Stakeholder Reporting

1. Collect the Outcome

Identify what ran, what passed, what failed, and what was skipped.
Identify whether the failures block release confidence or are isolated.

2. Translate into Stakeholder Language

Explain business impact, not stack traces.
Group failures by user-facing risk.
Call out confidence level and next action clearly.

3. Troubleshooting

Problem: The raw output is noisy. Fix: Collapse it into impacted capability, confidence, and next action.