jovd83
- 176 skills
- 0 followers
- 6 hours ago last updated
- ▌ Backlog Story Generator · jovd83 bundleGenerate structured epics, backlog-ready user stories, and ticket-import packs from requirements, discovery notes, workshops, SOPs, existing backlog folders, or an observed codebase. Use to decompose scope into epics, write user stories with Gherkin acceptance criteria, preserve numbering, validate, or export to Jira, Azure DevOps, GitHub Issues, or Tulip.
- ▌ Acceptance Criteria Designer · jovd83 bundleGenerate acceptance criteria from user stories, PRDs, requirements, use cases, business rules, or tickets that have none yet — and refine, normalize, critique, or convert existing criteria. Output testable Gherkin, TDD, or sentence-based criteria, identify assumption/coverage gaps, or return a JSON contract.
- ▌ Agentic Bdd Test Case Mentor · jovd83 bundleReview, rewrite, generate, and assess BDD or Gherkin feature files, scenarios, and outlines from user stories, acceptance criteria, business rules, or example maps. Use to identify BDD anti-patterns, traceability or coverage gaps, weak Given-When-Then structure, overloaded scenarios, missing rule branches, or coaching-oriented improvements without framework-specific automation design.
- ▌ API Contract Sentinel · jovd83 bundleAudit implemented or generated API code against an authoritative contract (OpenAPI, AsyncAPI, JSON Schema, protobuf, or PRD). Use to detect endpoint drift, missing operations, schema mismatches, status-code errors, auth/header gaps, or contract ambiguities before merge or client generation.
- ▌ Automated Test Reviewer · jovd83 bundleUse when Codex needs to explain automated test scripts in business language, review test automation quality with findings-first output, or map functional/manual test cases to automated coverage across UI, API, and contract-testing frameworks.
- ▌ Defect Lifecycle Agent Skill · jovd83 bundleUse when Codex must report a newly discovered defect, implement an approved bug fix, or harden regression coverage and documentation around a known bug. This skill enforces repository-aware bug intake, failing confirmation tests before fixes, scoped verification, documentation updates when warranted, and a structured resolution report.
- ▌ Codebase Context · jovd83 bundleAnalyze a repository before engineering work begins and produce a concise context bundle covering structure, entry points, dependencies, tests, conventions, and likely risk areas. Use when the user asks for a codebase overview, wants a Phase 0 understanding pass, or when another skill would benefit from a grounded map of an unfamiliar project before implementation, review, or refactoring.
- ▌ Context Density Optimizer · jovd83 bundleAudit the active working context and remove token noise before deeper implementation, review, or planning work. Use when Codex has accumulated too many files, notes, logs, prior summaries, or reference documents and needs to decide what to keep, drop, condense, or defer. Especially useful after broad codebase sweeps, large documentation reads, debug-log dumps, multi-skill handoffs, or whenever context relevance, signal density, or token efficiency has become uncertain.
- ▌ Defensive Appsec Review Skill · jovd83 bundleUse when you need an authorized, non-destructive security review of repos, APIs, and cloud apps. Trigger for OWASP reviews, dependency/secret audits, scanner consolidation, and security reports. Use for AppSec triage. Do NOT use for offensive exploitation or unauthorized testing.
- ▌ Design Fidelity Auditor · jovd83 bundleAudit implemented UI code for design-system drift. Use to verify CSS, Tailwind, JSX, TSX, Vue, or Angular components honor the project's canonical design tokens, typography, spacing scale, interaction states, and visual conventions.
- ▌ Diagram Generator · jovd83 bundleDecide which diagrams to draw, what to put in them, and which tool fits — Mermaid, PlantUML, or draw.io. Plans content from code, requirements, schemas, or ADRs and hands off rendering to a sister skill (pretty-mermaid, PlantUML-skill, or drawio-skill). Do NOT render directly.
- ▌ Eu AI Act Hitl Oversight Skill · jovd83 bundleDesign, review, and retrofit human-oversight controls for autonomous agent systems with pause, review, resume, reject, or halt behavior. Use for EU AI Act Article 12/14 logging, human handovers, typed review-decision contracts, reviewer reports, timeout/escalation rules, or critiques of unsafe approval flows.
- ▌ Greenfield Architecture Planner · jovd83 bundlePlan architecture for brand-new software products before bootstrap or implementation. Use when specs, acceptance criteria, personal/org/project/workspace context, constraints, stack preferences, or principles need decisions on stack, boundaries, data model, APIs, security, deployment, validation, ADRs, or handoff.
- ▌ Implementation Task Planner · jovd83 bundleTurn approved product requirements, acceptance criteria, architecture plans, and repository context into executable implementation task plans. Use when a project needs test-first, dependency-aware tasks with traceability, file targets, validation commands, parallel work markers, open questions, and downstream skill-routing before coding starts.
- ▌ Leak Canary · jovd83 bundleScan, audit, or check a project, directory, file, CSV export, log, or workspace for data leaks — credentials, API keys, secrets, PII, or GDPR violations — before pushing to GitHub, committing, sharing with external partners, archiving, or releasing. Invoke whenever the user asks to scan for secrets, check for leaks, audit for PII, review for credentials, or wants to verify GDPR compliance of exported data or test fixtures. Detects hardcoded passwords, AWS/Google/GitHub/Stripe/OpenAI/Azure keys, JWT tokens, database connection strings, email addresses, credit card numbers, IBANs, and 20+ European national IDs (Belgian INSZ, Dutch BSN, French INSEE, Polish PESEL, Swedish Personnummer, UK NINO, Spanish DNI, German Steuer-ID, Italian Codice Fiscale, Romanian CNP, Irish PPS, Portuguese NIF, and more). Use this skill proactively when the user mentions leaks, secrets, credentials, PII, GDPR, personal data, sensitive data, pre-commit checks, release security gates, or data export reviews.
- ▌ Lifelike Synthetic Data Generator · jovd83 bundleGenerate realistic, population-shaped synthetic datasets for tests, demos, and fixtures. Trigger for CSV/JSON exports, locale-aware personal/company fields, seeded generation, custom regex formats, Belgian identifiers (INSZ, eID), and distribution-backed sampling. Runs a local generator instead of fabricating in-context.
- ▌ Loxberry Integrator · jovd83 bundleGenerate, review, or harden GitHub-ready LoxBerry plugin projects that integrate devices, services, APIs, or protocols with a Loxone Miniserver. Use for LoxBerry plugin scaffolding, MQTT Gateway topic mapping, REST/UDP/TCP/Modbus/WebSocket bridges, daemon and web UI generation, Loxone Config instructions, plugin.cfg/release.cfg creation, and validation of generated LoxBerry plugin repositories.
- ▌ Modern Dependency Guard · jovd83 bundleReview, validate, and modernize technology choices before suggesting code that depends on external packages, frameworks, SDKs, CLIs, or hosted services. Use to choose a stack, sanity-check dependencies, replace deprecated tools, suggest modern alternatives, or scan a Node.js package manifest.
- ▌
- ▌ Performance Testing Skill · jovd83 bundlePlan, execute, and analyze performance testing for APIs, web apps, and distributed systems. Trigger for load, stress, spike, endurance tests, scalability, latency/throughput, and SLO verification. Use for capacity planning and bottleneck analysis. Do NOT use for destructive DoS or unauthorized production saturation.
- ▌ Plantuml Skill · jovd83 bundleEnterprise-grade engine for rendering professional PlantUML and C4 diagrams. Optimized for system architecture visualization, sequence flow modeling, and high-fidelity project documentation.
- ▌ Principal Audit Refactor · jovd83 bundleAudit a local software project, produce a severity-ranked engineering review, and execute an approval-gated refactor plan. Use when Codex needs to assess prototype-quality or inconsistent codebases, run stack-aware checks, write timestamped audit artifacts, and then implement production-grade improvements with explicit safety boundaries, report contracts, and refactoring discipline.
- ▌ Repository Bootstrapper Skill · jovd83 bundleCreate a new repository scaffold from approved architecture and implementation plans. Use when the user asks to bootstrap, scaffold, initialize, or create the initial project repository, including stack adapter selection, baseline files, planning artifact preservation, validation commands, setup summary, and safe handling of file-writing approvals.
- ▌ Project Constitution Skill · jovd83 bundleUse this skill when a user needs to create, update, or review a project constitution for a software project: an agent-readable governance document that defines durable product, engineering, architecture, testing, UX/accessibility, security/privacy, release, memory, and skill-routing principles before or during delivery. Prefer it for new projects, early-stage repositories, repo onboarding, SDLC kickoff, implementation planning, or when downstream agents need explicit quality gates and decision guardrails. Do not use it to choose a full architecture, write implementation code, or store cross-project policy unless the user supplied it.
- ▌ Project Genesis Chain · jovd83 bundleOrchestrate a complete greenfield software project from a raw idea to a release-ready repository using the existing agent skill portfolio. Use when the user wants to create a new project from scratch, run a spec-driven or SDLC-style project chain, bootstrap a repo, produce specs, plan architecture, generate implementation tasks, build the first slice, verify quality, and prepare release artifacts.
- ▌ Prompt Efficacy Scorer · jovd83 bundleAudit and improve prompts for clarity, consistency, instruction hierarchy, verbosity, and model fit. Use to review, score, tighten, debug, or optimize a prompt, system prompt, agent instructions, or template, or deliver a scorecard plus an optimized rewrite.
- ▌ Prototype Sketching Skill · jovd83 bundleUse when a working Angular, React, Vue, or static web app must look hand-sketched (Balsamiq wireframe, Sharpie marker, pencil, doodle, or blueprint) for a client demo, so clients read it as a draft and understand it is not production. Applies a reversible, non-destructive visual skin with an adjustable sketchiness level (0-100%) without touching components, markup, routing, state, or any logic.
- ▌ Release Manager Skill · jovd83 bundleValidate and prepare GitHub releases. Trigger for: SemVer changelogs, version bumps, release commits, CI/CD monitoring, and repo bootstrap.
- ▌ Responsive Testing · jovd83 bundleUse when an agent must plan, add, extend, or run responsive frontend testing across phones, tablets, laptops, desktops, or large screens, reuse existing tests before creating new ones, and generate a normalized responsive testing report in markdown, json, or html.
- ▌ Shared Memory · jovd83 bundleManage persistent cross-agent knowledge across agents, skills, and repos. Trigger to assess, retrieve, validate, or deprecate shared conventions, prompts, and org defaults. ALWAYS trigger on "remember", "save", or "note" for cross-turn info.
- ▌ Skill Dispatcher · jovd83 bundleHigh-performance routing engine for AI AgentSkills. Classifies user intent, scans for specialized skills, and generates optimal dispatch decisions (HANDOFF, SEQUENCE, or NO_MATCH). Use this to manage complexity in large skill environments and ensure the best-equipped skill handles every task.
- ▌ Slide Deck Preparation · jovd83 bundleConvert source material into grounded, presentation-ready slide deck outlines. Use when Codex needs to plan, audit, restructure, or enrich a presentation from URLs, articles, papers, transcripts, notes, documents, or an existing deck outline, with explicit audience framing, narrative arc, slide archetypes, speaker notes, visual guidance, and source citations.
- ▌ Stack Aware Unit Testing Skill · jovd83 bundleStack-aware unit and component test planning, authoring, and review. Use to inspect a codebase, detect the test framework, decide whether to reuse or introduce a stack, design coverage, write isolated tests without changing production, or report unit-test gaps and risks.
- ▌ Tss Test Case Reviewer · jovd83 bundleUse when the user wants to review, audit, critique, score, or mentor drafted software test cases, manual scenarios, UAT cases, or test suites for requirement traceability, coverage gaps, technical correctness, standards compliance, weak expected results, or TSS or TDD-style test design quality before execution, automation, or sign-off.
- ▌ Test Analysis Skill · jovd83 bundleUse when reviewing use cases, user stories, acceptance criteria, business requirements, or specifications for testability, ambiguity, requirement quality, delivery risk, or missing decisions before implementation or test design. For static reviews, risk-based analysis, and readiness triage. Do not use when writing tests or code.
- ▌ Test Artifact Export Skill · jovd83 bundleFormat already-designed test cases or artifacts into review-ready markdown, TDD case specs, scenario notes, BDD/Gherkin features, Xray Gherkin bundles, Zephyr Scale CSV, TestLink, or TestRail mappings. Use when test logic exists and Codex must normalize and render it for review or import.
- ▌ Test Lifecycle Skill · jovd83 bundleUse when the user wants end-to-end testing for a change — running a requirement, feature, webapp, UI, batch job, API, or release through the full 13-phase lifecycle (intake → HITL design → analysis → strategy → design → quality gate → data prep → export → automation + manual track in parallel → execution → functional review → heal loop → final report). Dispatches to phase-specific skills and pauses at HITL gates for approval. Use whenever the user asks to "test this end-to-end", "plan and execute testing", "run the test chain", or "deliver a verified, documented test pass". Do not use for one-off planning (use test-strategy-skill) or one-off case design (use test-design-orchestrator).
- ▌ Test Strategy Skill · jovd83 bundleUse when designing a test strategy or test plan for a requirement, feature, webapp, UI, batch job, API, or release. Produces a structured strategy doc that selects test levels and types, picks automation lanes per stack, derives exit criteria, prioritizes scenarios by risk, and splits work between automation and a manual track. Use whenever the user asks to plan, scope, strategize, or decide what to test, even if they do not say "strategy". Do not use for designing individual test cases (use test-design-orchestrator) or for analyzing requirement quality (use test-analysis-skill).
- ▌ Token Usage Cost Report · jovd83 bundleUse when an agent must produce an auditable token-usage and cost report from structured runtime evidence, normalized usage bundles, or repository-level report sets. This skill discovers trustworthy evidence, resolves official pricing, refuses transcript-only estimation, and generates provenance-backed Markdown, HTML, and JSON artifacts with explicit exact, partial, estimated, or unsupported cost labels.
- ▌ Skill Vetting Reporter · jovd83 bundleSecurity & trust vetting for an AgentSkill (folder, SKILL.md, zip, or single script) before it is installed or approved. Runs a mandatory open-source scanner gate (Cisco skill-scanner, NVIDIA SkillSpector, Snyk Agent Scan, sentry/skill-scanner), then static heuristics, and produces a draft review report — file inventory, executable surface, findings by severity, an OWASP Agentic Skills Top 10 (AST01-AST10) coverage map, a red-flag checklist, a suggested review tier (0-3), and reviewer sign-off blocks. Use this whenever someone asks "is this skill safe", "vet/review/scan this skill or SKILL.md or script", "run the vetting on skill X", "should I install this skill", or when a skill must pass the AgentSkills review flow. Also use it to re-vet an updated skill and diff the reports. It assists review and never approves anything on its own.
- ▌ Example Weather Fetcher · jovd83 bundleExample fixture skill bundled with skill-vetting-reporter. It fetches a public weather forecast for a city and returns a one-line summary. It exists only to demonstrate what a vetting report looks like — including a deliberate false positive — and is not meant to be installed or used for real work.
- ▌ Skill YAML Cleanup · jovd83 bundleAudit and reduce YAML frontmatter bloat in SKILL.md files. Trigger to: scan skill directories, identify oversized frontmatter, propose deduplication/flattening/migration optimizations, and apply approved changes. Requires user approval before writing.
- ▌
- ▌
- ▌
- ▌
- ▌ Junit5 Skill · jovd83 bundleUse 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.
- ▌ Junit5 CI · jovd83 bundleUse 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.
- ▌ Junit5 Core · jovd83 bundleUse when Codex needs to create, run, debug, evaluate, refactor, or correct JUnit 5 tests across component, integration, slice, repository, service, smoke, or regression scenarios.
- ▌ Junit5 Analysis · jovd83 bundleUse 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.
- ▌ Junit5 Migration · jovd83 bundleUse when Codex needs to migrate tests from JUnit 3 or JUnit 4 to JUnit 5, replace runners and rules, reduce Vintage usage, and preserve behavioral compatibility during modernization.
- ▌ Junit5 Extensions · jovd83 bundleUse when Codex needs to create, review, or debug JUnit 5 extensions, custom annotations, lifecycle callbacks, parameter resolvers, or reusable execution hooks.
- ▌ Junit5 Architecture · jovd83 bundleUse 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.
- ▌ Junit5 Documentation Tests · jovd83Use when Codex needs to document JUnit 5 automation code with clear scenario intent, suite purpose, traceability, or maintainable human-readable explanations.
- ▌ Junit5 Reporting Stakeholder · jovd83Use when Codex needs to summarize JUnit 5 test execution results for non-technical stakeholders in clear business-oriented language instead of raw runner output.
- ▌ Junit5 Installer Vscode Codex · jovd83Use when Codex needs to help configure Visual Studio Code for JUnit 5 development, execution, debugging, and Codex-driven workflows in a JVM project.
- ▌ Junit5 Documentation Root Cause · jovd83Use 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.
- ▌ Junit5 Installer Intellij Junie · jovd83Use when Codex needs to help configure IntelliJ IDEA for JUnit 5 development, execution, debugging, and Junie-style workflows in a JVM project.
- ▌ Test Design Orchestrator · jovd83 bundleTurn requirements, user stories, acceptance criteria, business rules, use cases, or state models into structured test artifacts. Selects the best black-box test design technique and routes work to the matching subskill. For format-only work, prefer test-artifact-export-skill.
- ▌ Decision Table · jovd83Use this skill when requirements describe discrete business rules, multiple conditions, or outcome logic that should be modeled as a rule table.
- ▌ State Transition · jovd83Use this skill when a system has discrete states, events, guards, or lifecycle phases and Codex needs transition-focused test design.
- ▌ Use Case Testing · jovd83Use this skill when requirements are expressed as actor-system interactions with preconditions, main flows, alternate flows, and postconditions.
- ▌ Technique Selector · jovd83Use this skill when Codex needs to choose the best black-box test design technique for a requirement, user story, rule set, workflow, or state model before generating tests.
- ▌ Test Case Formatter · jovd83Compatibility bridge for the old test-design-orchestrator formatter entrypoint. Prefer the standalone `test-artifact-export-skill` skill for formatting existing test cases, BDD/TDD/plain-text rendering, and tool-export artifacts.
- ▌ Boundary Value Analysis · jovd83Use this skill when a requirement contains ordered values such as ranges, lengths, dates, counts, or sequence limits and Codex needs boundary-focused test scenarios.
- ▌ Equivalence Partitioning · jovd83Use this skill when Codex needs to derive representative tests from input classes that should behave the same within each valid or invalid partition.
- ▌ Classification Tree Nwise · jovd83Use this skill when Codex needs to model interacting parameters and generate reduced pairwise or n-wise combinations instead of an impractical full Cartesian set.
- ▌ Acceptance Criteria To Test Cases · jovd83Use this skill when Codex needs to convert user stories or acceptance criteria into traceable behavior-focused scenarios or structured test cases.
- ▌ Playwright Skill · jovd83 bundleFlagship Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing Playwright. Routes E2E, API, component, visual, accessibility, CI/CD, coverage, docs, CLI automation, and handoff workflows.
- ▌ Playwright CI · jovd83 bundleCI and delivery skill for Playwright automation. Use when Codex needs to design, debug, or optimize Playwright execution in GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, sharded pipelines, artifact workflows, or shared setup and teardown.
- ▌ Playwright Pom · jovd83 bundleTest-architecture skill for Playwright page objects, fixtures, and helpers. 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.
- ▌ Playwright Core · jovd83 bundleCore Playwright implementation skill for resilient test authoring and debugging. Use when Codex needs practical Playwright guidance for locators, assertions, fixtures, authentication, network behavior, API testing, component testing, debugging, framework-specific recipes, or broader test architecture decisions.
- ▌ Playwright Analysis Requirements · jovd83 bundleRequirements-analysis skill for Playwright 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.
- ▌ Playwright Migration · jovd83 bundleMigration skill for moving existing UI automation to Playwright. Use when Codex needs to translate Cypress or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.
- ▌ Playwright Mapper Xray · jovd83 bundleTest-management mapping skill for Xray. Use when Codex needs to apply authoritative Xray test keys or issue IDs back into local Playwright docs, tags, or annotations for reliable traceability and reporting.
- ▌ Playwright Orchestrator · jovd83 bundleCentral entrypoint for broad or ambiguous Playwright requests. Use when Codex needs to classify the user's testing goal, choose the right Playwright subskill, and move from intent to implementation, planning, documentation, execution, or reporting without unnecessary menu-driven back-and-forth.
- ▌ Playwright Mapper Zephyr · jovd83 bundleTest-management mapping skill for Zephyr Scale. Use when Codex needs to apply authoritative Zephyr test keys back into local Playwright docs, titles, or annotations so execution and planning artifacts stay aligned.
- ▌ Playwright CLI · jovd83 bundleBrowser-automation skill for terminal-driven Playwright work. Use when Codex needs to navigate websites, inspect pages, interact with forms, capture screenshots or traces, manage browser sessions, mock requests, or generate test code through a local `playwright-cli` workflow instead of writing a full test first.
- ▌ Playwright Reporter Xray · jovd83 bundleTest-management reporting skill for Xray. Use when Codex needs to publish Playwright execution results into Xray or Jira using the project's mappings, import format, and chosen reporting flow.
- ▌ Playwright Mapper Testlink · jovd83 bundleTest-management mapping skill for TestLink. Use when Codex needs to apply authoritative TestLink case IDs back into local Playwright docs, titles, or annotations so the repository can trace automation to imported TestLink records.
- ▌ Playwright Mapper Testrail · jovd83 bundleTest-management mapping skill for TestRail. Use when Codex needs to apply authoritative TestRail case IDs back into local Playwright docs, titles, or annotations so automation can be traced or reported accurately.
- ▌ Playwright Reporter Zephyr · jovd83 bundleTest-management reporting skill for Zephyr Scale. Use when Codex needs to publish Playwright execution results into Zephyr using the project's mappings, run configuration, and chosen reporting flow.
- ▌ Playwright Transformer Xray · jovd83 bundleLegacy Playwright-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 Playwright-local conventions must be preserved explicitly.
- ▌ Playwright Reporter Testlink · jovd83 bundleTest-management reporting skill for TestLink. Use when Codex needs to publish Playwright execution results into TestLink using the project's mappings, environment configuration, and chosen reporting flow.
- ▌ Playwright Reporter Testrail · jovd83 bundleTest-management reporting skill for TestRail. Use when Codex needs to publish Playwright execution results into TestRail using the project's mappings, run configuration, and chosen reporting flow.
- ▌ Playwright Documentation Tests · jovd83 bundleAutomation-code documentation skill for Playwright suites. Use when Codex needs to add or improve human-readable comments, docblocks, or file-level explanations around existing Playwright tests without drowning the code in redundant commentary.
- ▌ Playwright Transformer Zephyr · jovd83 bundleLegacy Playwright-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 Playwright-local conventions must be preserved explicitly.
- ▌ Playwright Coverage Plan Review · jovd83 bundleCoverage-plan review skill for Playwright 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.
- ▌ Playwright Reporting Stakeholder · jovd83 bundleStakeholder-reporting skill for Playwright execution results. Use when Codex needs to turn raw Playwright runs into a concise, non-technical summary of tested scope, release health, business impact, and recommended next actions.
- ▌ Playwright Transformer Testlink · jovd83 bundleLegacy Playwright-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 Playwright-local conventions must be preserved explicitly.
- ▌ Playwright Transformer Testrail · jovd83 bundleLegacy Playwright-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 Playwright-local conventions must be preserved explicitly.
- ▌ Handover · jovd83 bundleUse when Playwright work must be handed from one operator to another, including at task completion, during mid-task pauses, after a blocker, or before review. Create a structured handover that records what was completed, where execution stopped, what remains, validation status, blockers, and the exact steps to resume safely.
- ▌ Playwright Coverage Matrix Auto Sync · jovd83 bundleCoverage-maintenance skill for Playwright 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.
- ▌ Playwright Installer Vscode Codex · jovd83 bundleEditor-setup skill for Playwright plus OpenAI Codex in Visual Studio Code. Use when Codex needs to help configure a practical VS Code environment for Playwright authoring, execution, debugging, and local skill usage.
- ▌ Playwright Coverage Plan Generation · jovd83 bundleCoverage-planning skill for Playwright work. Use when Codex needs to turn confirmed requirements into a structured, risk-aware Playwright coverage plan with scenarios, execution types, priorities, and traceability.
- ▌ Playwright Documentation Root Cause · jovd83 bundleFailure-analysis skill for Playwright 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.
- ▌ Playwright Installer Intellij Junie · jovd83 bundleEditor-setup skill for Playwright plus Junie in IntelliJ IDEA. Use when Codex needs to help configure an IntelliJ-based Playwright workflow with the Junie assistant and verify the environment is ready for authoring and running tests.
- ▌ Session State · jovd83 bundleUse when Playwright work spans multiple sessions or operators and a live resume pointer is needed. Maintain a current state file that records the latest completed step, current in-progress step, remaining work, blockers, touched files, resume commands, validation snapshot, and links to the latest handover.
- ▌ Playwright Documentation Bdd · jovd83 bundleLegacy Playwright-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 Playwright-local conventions must be preserved explicitly.
- ▌ Playwright Documentation Tdd · jovd83 bundleLegacy Playwright-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 Playwright-local conventions must be preserved explicitly.