Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

restassured-orchestrator

Estrelas2

Forks0

Atualizado13 de maio de 2026 às 06:22

Use when Codex receives a generic Rest Assured or service-testing request and must route the work into planning, implementation, documentation, execution, CI, virtualization, or test-management flows.

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/restassured-skill

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	restassured-orchestrator
description	Use when Codex receives a generic Rest Assured or service-testing request and must route the work into planning, implementation, documentation, execution, CI, virtualization, or test-management flows.
metadata	{"author":"jovd83","version":"1.0","dispatcher-category":"testing","dispatcher-capabilities":"api-test-orchestration, restassured-routing","dispatcher-accepted-intents":"route_api_testing_work, orchestrate_restassured_task","dispatcher-input-artifacts":"user_request, repo_context, api_requirements, api_contract, failure_output","dispatcher-output-artifacts":"routing_decision, routing_request, execution_plan","dispatcher-stack-tags":"restassured, orchestration, api-testing","dispatcher-risk":"medium","dispatcher-writes-files":false}

Rest Assured Orchestrator

1. Clarify the Goal

Ask for the primary goal if the user request is ambiguous.
Classify the request into one of these buckets:
1. Bootstrap a test module.
2. Analyze requirements.
3. Analyze OpenAPI or Swagger contracts.
4. Analyze WSDL or SOAP contracts.
5. Generate or review coverage.
6. Implement or fix tests.
7. Stub or virtualize downstream services.
8. Configure CI.
9. Document tests, traceability, quality, or failures.
10. Regenerate a bundled reporting set.
11. Transform, map, or report results to a test-management tool.

2. Route

Use ../bootstrap/SKILL.md for missing setup.
Use ../analysis/requirements/SKILL.md for stories, epics, and acceptance criteria.
Use ../analysis/contracts/SKILL.md for REST contracts.
Use ../analysis/contracts-soap/SKILL.md for SOAP contracts.
Use ../coverage_plan/generation/SKILL.md for scenario generation.
Use ../coverage_plan/review/SKILL.md for explicit approval.
Use ../core/SKILL.md for implementation and defect fixing.
Use ../virtualization/SKILL.md for WireMock and fault injection.
Use ../ci/SKILL.md for pipeline work.
Use ../documentation/report-bundle/SKILL.md when the goal is to refresh the reporting set as one operation.
Use ../documentation/*/SKILL.md for documentation and diagnosis that is not test-case formatting.
Dispatch render_test_artifact through skill-dispatcher for test-case formatting and export artifacts. Use C:\projects\skills\test-artifact-export-skill\SKILL.md only as a compatibility fallback.
Use ../mappers or ../reporters for external execution tools.
When routing into test-case documentation, treat docs/tests/<feature>/ as the canonical home for scenario-level docs and treat docs/testing/ as index and reporting space.

3. Enforce the Sequence

Require approved requirements before generating a coverage plan.
Require an approved coverage plan before large-scale test implementation when the scenarios are AI-defined.
Skip approval only when the user already supplied the test cases or explicitly asked for direct implementation.
When the user asks for narrative documentation but not a format, choose TDD, BDD, plain text, or mixed mode explicitly before writing files.

4. Read When Needed

Read routing-matrix.md for trigger phrases and routing shortcuts.

5. Examples

Input: Help me test this payments service. Output: Ask whether the goal is setup, planning, implementation, CI, documentation, or reporting.
Input: Create scenarios from this OpenAPI and then implement them. Output: Route to contracts analysis, coverage generation, review, then core.
Input: Rebuild the coverage and quality reports for this API module. Output: Route to ../documentation/report-bundle/SKILL.md.
Input: Check whether the narrative docs still match the API tests. Output: Route to ../documentation/documentation-sync/SKILL.md.
Input: Document these approved payment scenarios, but keep each scenario separate. Output: Route to dispatcher intent render_test_artifact and store the canonical files under docs/tests/payments/.

6. Troubleshooting

Problem: The user mixes setup and implementation. Fix: Complete bootstrap first, then move into core.
Problem: The user asks for implementation without requirements or contracts. Fix: Proceed only if the requested tests are already enumerated or narrow enough to infer safely.
Problem: Documentation requests default to one oversized markdown file. Fix: Split TDD and plain-text docs into one scenario file per behavior and use feature files only where BDD grouping adds value.
Problem: The target exporter skill changes or is temporarily unavailable. Fix: Go through skill-dispatcher first and treat the direct exporter path as fallback only.

Mais deste repositório

mesmo repositório

restassured-skill

jovd83/restassured-skill

Use when Codex needs to design, implement, run, document, or report Rest Assured API tests for REST services, contract-driven service tests, JUnit 5 automation, CI pipelines, or test-management integrations.

2026-05-132

restassured-analysis-contracts

jovd83/restassured-skill

Use when Codex needs to derive Rest Assured test scenarios from OpenAPI or Swagger contracts, including endpoints, methods, schemas, auth rules, status codes, and error conditions.

2026-05-132

restassured-analysis-contracts-soap

jovd83/restassured-skill

Use when Codex needs to derive service-test scenarios from WSDL or SOAP contracts and translate them into HTTP and XML checks that can still be implemented with Rest Assured where appropriate.

2026-05-132

restassured-analysis-requirements

jovd83/restassured-skill

Use when Codex needs to extract testable API behavior from epics, user stories, acceptance criteria, tickets, markdown docs, or other prose requirements before generating Rest Assured scenarios.

2026-05-132

restassured-bootstrap

jovd83/restassured-skill

Use when Codex needs to scaffold, retrofit, or normalize a Java Rest Assured test module with JUnit 5, Maven or Gradle, shared specifications, and an initial runnable smoke test.

2026-05-132

restassured-ci

jovd83/restassured-skill

Use when Codex needs to configure or troubleshoot Rest Assured API tests in CI pipelines, including JUnit 5 execution, tags, Docker, containers, artifacts, quality gates, and provider-specific pipeline examples.

2026-05-132

name	restassured-orchestrator
description	Use when Codex receives a generic Rest Assured or service-testing request and must route the work into planning, implementation, documentation, execution, CI, virtualization, or test-management flows.
metadata	{"author":"jovd83","version":"1.0","dispatcher-category":"testing","dispatcher-capabilities":"api-test-orchestration, restassured-routing","dispatcher-accepted-intents":"route_api_testing_work, orchestrate_restassured_task","dispatcher-input-artifacts":"user_request, repo_context, api_requirements, api_contract, failure_output","dispatcher-output-artifacts":"routing_decision, routing_request, execution_plan","dispatcher-stack-tags":"restassured, orchestration, api-testing","dispatcher-risk":"medium","dispatcher-writes-files":false}

Rest Assured Orchestrator

1. Clarify the Goal

Ask for the primary goal if the user request is ambiguous.
Classify the request into one of these buckets:
1. Bootstrap a test module.
2. Analyze requirements.
3. Analyze OpenAPI or Swagger contracts.
4. Analyze WSDL or SOAP contracts.
5. Generate or review coverage.
6. Implement or fix tests.
7. Stub or virtualize downstream services.
8. Configure CI.
9. Document tests, traceability, quality, or failures.
10. Regenerate a bundled reporting set.
11. Transform, map, or report results to a test-management tool.

2. Route

Use ../bootstrap/SKILL.md for missing setup.
Use ../analysis/requirements/SKILL.md for stories, epics, and acceptance criteria.
Use ../analysis/contracts/SKILL.md for REST contracts.
Use ../analysis/contracts-soap/SKILL.md for SOAP contracts.
Use ../coverage_plan/generation/SKILL.md for scenario generation.
Use ../coverage_plan/review/SKILL.md for explicit approval.
Use ../core/SKILL.md for implementation and defect fixing.
Use ../virtualization/SKILL.md for WireMock and fault injection.
Use ../ci/SKILL.md for pipeline work.
Use ../documentation/report-bundle/SKILL.md when the goal is to refresh the reporting set as one operation.
Use ../documentation/*/SKILL.md for documentation and diagnosis that is not test-case formatting.
Dispatch render_test_artifact through skill-dispatcher for test-case formatting and export artifacts. Use C:\projects\skills\test-artifact-export-skill\SKILL.md only as a compatibility fallback.
Use ../mappers or ../reporters for external execution tools.
When routing into test-case documentation, treat docs/tests/<feature>/ as the canonical home for scenario-level docs and treat docs/testing/ as index and reporting space.

3. Enforce the Sequence

Require approved requirements before generating a coverage plan.
Require an approved coverage plan before large-scale test implementation when the scenarios are AI-defined.
Skip approval only when the user already supplied the test cases or explicitly asked for direct implementation.
When the user asks for narrative documentation but not a format, choose TDD, BDD, plain text, or mixed mode explicitly before writing files.

4. Read When Needed

Read routing-matrix.md for trigger phrases and routing shortcuts.

5. Examples

Input: Help me test this payments service. Output: Ask whether the goal is setup, planning, implementation, CI, documentation, or reporting.
Input: Create scenarios from this OpenAPI and then implement them. Output: Route to contracts analysis, coverage generation, review, then core.
Input: Rebuild the coverage and quality reports for this API module. Output: Route to ../documentation/report-bundle/SKILL.md.
Input: Check whether the narrative docs still match the API tests. Output: Route to ../documentation/documentation-sync/SKILL.md.
Input: Document these approved payment scenarios, but keep each scenario separate. Output: Route to dispatcher intent render_test_artifact and store the canonical files under docs/tests/payments/.

6. Troubleshooting

Problem: The user mixes setup and implementation. Fix: Complete bootstrap first, then move into core.
Problem: The user asks for implementation without requirements or contracts. Fix: Proceed only if the requested tests are already enumerated or narrow enough to infer safely.
Problem: Documentation requests default to one oversized markdown file. Fix: Split TDD and plain-text docs into one scenario file per behavior and use feature files only where BDD grouping adds value.
Problem: The target exporter skill changes or is temporarily unavailable. Fix: Go through skill-dispatcher first and treat the direct exporter path as fallback only.