jovd83
- 176 skills
- 0 followers
- 1 day ago last updated
- ▌ Playwright Documentation Plaintext · jovd83 bundleLegacy Playwright-specific alias for plain-text case formatting. Prefer the standalone `test-artifact-export-skill` skill for lightweight narrative case output, and use this only when Playwright-local conventions must be preserved explicitly.
- ▌ Cypress Coverage Matrix Auto Sync · jovd83 bundleCoverage-maintenance skill for Cypress planning and documentation. Use when Codex needs to synchronize coverage plans, scenario IDs, traceability links, and summary counts after tests, requirements, or narrative test documents change.
- ▌ Cypress Installer Vscode Codex · jovd83 bundleEditor-setup skill for Cypress plus OpenAI Codex in Visual Studio Code. Use when Codex needs to help configure a practical VS Code environment for Cypress authoring, execution, debugging, and local skill usage.
- ▌ Cypress Coverage Plan Generation · jovd83 bundleCoverage-planning skill for Cypress work. Use when Codex needs to turn confirmed requirements into a structured, risk-aware Cypress coverage plan with scenarios, execution types, priorities, and traceability.
- ▌ Cypress Documentation Root Cause · jovd83 bundleFailure-analysis skill for Cypress runs. Use when Codex needs to investigate a failing test, distinguish likely product bugs from test issues, and produce a concise developer-focused root-cause report backed by evidence.
- ▌ Cypress Installer Intellij Junie · jovd83 bundleEditor-setup skill for Cypress plus Junie in IntelliJ IDEA. Use when Codex needs to help configure a practical JetBrains environment for Cypress authoring, execution, debugging, and local skill usage.
- ▌ Cypress Session State Compat · jovd83 bundleUse when you need the legacy Cypress session-state entrypoint path; record session state in the canonical Cypress handover workflow.
- ▌ Cypress Documentation Bdd · jovd83 bundleLegacy Cypress-specific alias for BDD case formatting. Prefer the standalone `test-artifact-export-skill` skill for Gherkin, BDD, and export-ready case rendering, and use this only when Cypress-local conventions must be preserved explicitly.
- ▌ Cypress Documentation Tdd · jovd83 bundleLegacy Cypress-specific alias for TDD-style case documentation. Prefer the standalone `test-artifact-export-skill` skill for formatting approved test cases or building export-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.
- ▌ Cypress Handover · jovd83 bundleUse when you need a Cypress task handover that preserves status, session state, blockers, and exact resume steps for a human or later agent.
- ▌ Cypress Documentation Plaintext · jovd83 bundleLegacy Cypress-specific alias for plain-text case formatting. Prefer the standalone `test-artifact-export-skill` skill for lightweight narrative case output, and use this only when Cypress-local conventions must be preserved explicitly.
- ▌ Cypress Skill · jovd83 bundleFlagship Cypress skill pack for planning, authoring, debugging, documenting, and operationalizing Cypress. Routes E2E, API, component, visual, accessibility, CI/CD, coverage, docs, CLI automation, and handoff workflows.
- ▌ Cypress CI · jovd83 bundleCI and delivery skill for Cypress automation. Use when Codex needs to design, debug, or optimize Cypress execution in GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, sharded pipelines, artifact workflows, or shared setup and teardown.
- ▌ Cypress Pom · jovd83 bundleTest-architecture skill for Cypress page objects, fixtures, helpers, and custom commands. Use when Codex needs to decide whether to introduce a Page Object Model, how to structure page objects, and how to separate browser state, UI behavior, and stateless utilities cleanly.
- ▌ Cypress Core · jovd83 bundleBattle-tested Cypress patterns for E2E, API, component, visual, accessibility, and security testing. Covers selectors, assertions, hooks, intercepts, auth flows, debugging, and framework recipes for React, Next.js, Vue, and Angular.
- ▌ Cypress Analysis Requirements · jovd83 bundleRequirements-analysis skill for Cypress planning and implementation. Use when Codex needs to extract testable behaviors, acceptance criteria, risks, dependencies, or open questions from tickets, specs, markdown docs, or other requirement sources before writing tests or coverage plans.
- ▌ Cypress Migration · jovd83 bundleMigration skill for moving existing UI automation to Cypress. Use when Codex needs to translate Playwright or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.
- ▌
- ▌ Cypress Mapper Xray · jovd83 bundleTest-management mapping skill for Xray. Use when Codex needs to apply authoritative Xray issue or case IDs back into local Cypress docs, titles, or annotations so the repository can trace automation to imported Xray records.
- ▌ Cypress Orchestrator · jovd83 bundleCentral entrypoint for broad or ambiguous Cypress requests. Use when Codex needs to classify the user's testing goal, choose the right Cypress subskill, and move from intent to implementation, planning, documentation, execution, or reporting without unnecessary menu-driven back-and-forth.
- ▌ Cypress Mapper Zephyr · jovd83 bundleTest-management mapping skill for Zephyr Scale. Use when Codex needs to apply authoritative Zephyr case IDs back into local Cypress docs, titles, or annotations so the repository can trace automation to imported Zephyr records.
- ▌ Cypress Reporter Xray · jovd83 bundleTest-management reporting skill for Xray. Use when Codex needs to publish Cypress execution results into Xray using the project's mappings, environment configuration, and chosen reporting flow.
- ▌ Cypress Mapper Testlink · jovd83 bundleTest-management mapping skill for TestLink. Use when Codex needs to apply authoritative TestLink case IDs back into local Cypress docs, titles, or annotations so the repository can trace automation to imported TestLink records.
- ▌ Cypress Mapper Testrail · jovd83 bundleTest-management mapping skill for TestRail. Use when Codex needs to apply authoritative TestRail case IDs back into local Cypress docs, titles, or annotations so the repository can trace automation to imported TestRail records.
- ▌ Cypress Reporter Zephyr · jovd83 bundleTest-management reporting skill for Zephyr Scale. Use when Codex needs to publish Cypress execution results into Zephyr using the project's mappings, environment configuration, and chosen reporting flow.
- ▌ Cypress Transformer Xray · jovd83 bundleLegacy Cypress-specific alias for Xray case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into Xray-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.
- ▌ Cypress Reporter Testlink · jovd83 bundleTest-management reporting skill for TestLink. Use when Codex needs to publish Cypress execution results into TestLink using the project's mappings, environment configuration, and chosen reporting flow.
- ▌ Cypress Reporter Testrail · jovd83 bundleTest-management reporting skill for TestRail. Use when Codex needs to publish Cypress execution results into TestRail using the project's mappings, environment configuration, and chosen reporting flow.
- ▌ Cypress Documentation Tests · jovd83 bundleAutomation-code documentation skill for Cypress suites. Use when Codex needs to add or improve human-readable comments, docblocks, or file-level explanations around existing Cypress tests without drowning the code in redundant commentary.
- ▌ Cypress Transformer Zephyr · jovd83 bundleLegacy Cypress-specific alias for Zephyr case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into Zephyr-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.
- ▌ Cypress Coverage Plan Review · jovd83 bundleCoverage-plan review skill for Cypress work. Use when Codex needs to present a proposed coverage plan, surface assumptions and tradeoffs, collect user feedback, and secure explicit approval before large implementation or documentation work.
- ▌ Cypress Reporting Stakeholder · jovd83 bundleStakeholder-reporting skill for Cypress execution results. Use when Codex needs to turn raw Cypress runs into a concise, non-technical summary of tested scope, release health, business impact, and recommended next actions.
- ▌ Cypress Transformer Testlink · jovd83 bundleLegacy Cypress-specific alias for TestLink case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into TestLink-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.
- ▌ Cypress Transformer Testrail · jovd83 bundleLegacy Cypress-specific alias for TestRail case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into TestRail-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.
- ▌ Cypress Handover Compat · jovd83 bundleUse when you need the legacy Cypress handover entrypoint path; follow the canonical Cypress handover workflow in documentation/cypress-handover.
- ▌ Restassured Skill · jovd83 bundleUse 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.
- ▌ Restassured CI · jovd83 bundleUse 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.
- ▌ Restassured Core · jovd83 bundleUse when Codex needs to implement, refactor, debug, or extend Rest Assured API tests with JUnit 5, reusable request and response specifications, authentication helpers, DTOs, contract checks, and service-test best practices.
- ▌ Restassured Bootstrap · jovd83 bundleUse 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.
- ▌ Restassured Mapper Xray · jovd83 bundleUse when Codex needs to map Xray issue keys or execution references back to local Rest Assured API documentation or automation files.
- ▌ Restassured Orchestrator · jovd83 bundleUse 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.
- ▌ Restassured Mapper Zephyr · jovd83 bundleUse when Codex needs to map Zephyr case IDs or execution references back to local Rest Assured API documentation or automation files.
- ▌ Restassured Reporter Xray · jovd83 bundleUse when Codex needs to report Rest Assured API test execution results back to Xray through its API using local case mappings and execution evidence.
- ▌ Restassured Virtualization · jovd83 bundleUse when Codex needs to simulate downstream HTTP services for Rest Assured suites with WireMock, stub mappings, latency, retries, fault injection, or isolation from unstable third-party dependencies.
- ▌ Restassured Mapper Testlink · jovd83 bundleUse when Codex needs to map TestLink case IDs or execution references back to local Rest Assured API documentation or automation files.
- ▌ Restassured Mapper Testrail · jovd83 bundleUse when Codex needs to map TestRail case IDs or execution references back to local Rest Assured API documentation or automation files.
- ▌ Restassured Reporter Zephyr · jovd83 bundleUse when Codex needs to report Rest Assured API test execution results back to Zephyr through its API using local case mappings and execution evidence.
- ▌ Restassured Transformer Xray · jovd83 bundleLegacy Rest Assured-specific alias for Xray case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into Xray-ready artifacts, and use this only when Rest Assured-local conventions must be preserved explicitly.
- ▌ Restassured Analysis Contracts · jovd83 bundleUse 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.
- ▌ Restassured Reporter Testlink · jovd83 bundleUse when Codex needs to report Rest Assured API test execution results back to TestLink through its API using local case mappings and execution evidence.
- ▌ Restassured Reporter Testrail · jovd83 bundleUse when Codex needs to report Rest Assured API test execution results back to TestRail through its API using local case mappings and execution evidence.
- ▌ Restassured Documentation Tests · jovd83 bundleUse when Codex needs to add human-readable documentation to Rest Assured automation code, including class purpose, role boundaries, shared specs, and scenario intent.
- ▌ Restassured Transformer Zephyr · jovd83 bundleLegacy Rest Assured-specific alias for Zephyr case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into Zephyr-ready artifacts, and use this only when Rest Assured-local conventions must be preserved explicitly.
- ▌ Restassured Coverage Plan Review · jovd83 bundleUse when Codex needs to present a generated Rest Assured API coverage plan to the user, request explicit approval, and block implementation until the scope is confirmed.
- ▌ Restassured Analysis Requirements · jovd83 bundleUse 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.
- ▌ Restassured Reporting Stakeholder · jovd83 bundleUse when Codex needs to summarize Rest Assured API test execution for non-technical stakeholders in clear business terms instead of raw test runner output.
- ▌ Restassured Transformer Testlink · jovd83 bundleLegacy Rest Assured-specific alias for TestLink case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into TestLink-ready artifacts, and use this only when Rest Assured-local conventions must be preserved explicitly.
- ▌ Restassured Transformer Testrail · jovd83 bundleLegacy Rest Assured-specific alias for TestRail case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into TestRail-ready artifacts, and use this only when Rest Assured-local conventions must be preserved explicitly.
- ▌ Restassured Documentation Handover · jovd83 bundleUse when Codex needs to produce a concise handover for completed Rest Assured API testing work, including what changed, what remains open, and how to continue safely.
- ▌ Restassured Analysis Contracts Soap · jovd83 bundleUse 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.
- ▌ Restassured Coverage Plan Auto Sync · jovd83 bundleUse when Codex needs to keep Rest Assured API coverage plans, requirements mappings, and test-case documentation synchronized as scenarios are added, removed, or renamed.
- ▌ Restassured Installer Vscode Codex · jovd83 bundleUse when Codex needs to set up VS Code for Rest Assured API testing with Java, Maven or Gradle, JUnit 5, and Codex-driven workflow support.
- ▌ Restassured Coverage Plan Generation · jovd83 bundleUse when Codex needs to generate a Rest Assured API test coverage plan from approved requirements, OpenAPI or Swagger contracts, WSDL analysis, and explicit scope constraints.
- ▌ Restassured Documentation Root Cause · jovd83 bundleUse when Codex needs to analyze failing Rest Assured API tests, identify the most likely root cause, and produce a developer-focused failure diagnosis.
- ▌ Restassured Installer Intellij Junie · jovd83 bundleUse when Codex needs to set up IntelliJ IDEA for Rest Assured API testing with Java, Maven or Gradle, JUnit 5, and Junie-style workflow support.
- ▌ Restassured Documentation Report Bundle · jovd83 bundleUse when Codex needs to generate or refresh a bundled Rest Assured reporting set, including traceability, contract mismatches, coverage gaps, OpenAPI change impact, assertion strength, and the human-friendly HTML portal, with support for BDD, TDD, plain-text, mixed, or absent narrative documentation.
- ▌ Restassured Documentation Session State · jovd83 bundleUse when Codex needs to persist a durable resume checkpoint for Rest Assured API testing work so a human or later agent can see what is done, what is blocked, and exactly how to continue.
- ▌ Restassured Documentation Bdd · jovd83 bundleLegacy Rest Assured-specific alias for BDD case formatting. Prefer the standalone `test-artifact-export-skill` skill for Gherkin, BDD, and export-ready case rendering, and use this only when Rest Assured-local conventions must be preserved explicitly.
- ▌ Restassured Documentation Tdd · jovd83 bundleLegacy Rest Assured-specific alias for TDD-style case documentation. Prefer the standalone `test-artifact-export-skill` skill for formatting approved test cases or building export-ready artifacts, and use this only when Rest Assured-local conventions must be preserved explicitly.
- ▌ Restassured Documentation Sync · jovd83 bundleUse when Codex needs to keep Rest Assured narrative documentation synchronized with endpoint traceability, coverage rows, and executable tests across BDD, TDD, plain-text, mixed, or partially documented API suites.
- ▌ Restassured Documentation Contract Mismatches · jovd83 bundleUse when Codex needs to document differences between an API contract and the observed live Rest Assured runtime behavior so humans and later agents can implement tests safely and track drift explicitly.
- ▌ Restassured Documentation Coverage Gap Report · jovd83 bundleUse when Codex needs to highlight uncovered, partial, drift-only, or weakly covered API areas so humans can prioritize the next Rest Assured work instead of reading the full traceability report.
- ▌ Restassured Documentation Traceability Report · jovd83 bundleUse when Codex needs to produce a traceability report that maps API endpoints, methods, operations, coverage rows, Rest Assured tests, and narrative documentation references so humans and later agents can see exactly what is covered across BDD, TDD, plain-text, mixed, or absent documentation.
- ▌ Restassured Documentation Plaintext · jovd83 bundleLegacy Rest Assured-specific alias for plain-text case formatting. Prefer the standalone `test-artifact-export-skill` skill for lightweight narrative case output, and use this only when Rest Assured-local conventions must be preserved explicitly.
- ▌ Restassured Documentation Assertion Strength Report · jovd83 bundleUse when Codex needs to assess whether Rest Assured tests are weak, moderate, or strong based on the assertions they make, the amount of API behavior they verify, and whether they go beyond status-code checks.
- ▌ Restassured Documentation Openapi Change Impact Report · jovd83 bundleUse when Codex needs to compare two OpenAPI or Swagger contracts, identify added, removed, or changed operations and schemas, and map the impact back to existing Rest Assured coverage.