菜单
Coverage-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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when you need a Cypress task handover that preserves status, session state, blockers, and exact resume steps for a human or later agent.
Flagship 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.
Requirements-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.
CI 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.
Battle-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.
Coverage-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.
| name | cypress-coverage-matrix-auto-sync |
| description | Coverage-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. |
| metadata | {"author":"jovd83","version":"1.1","dispatcher-category":"testing","dispatcher-capabilities":"coverage-maintenance, cypress-coverage-sync","dispatcher-accepted-intents":"sync_cypress_coverage_artifacts","dispatcher-input-artifacts":"coverage_plan, test_suite, traceability_artifacts","dispatcher-output-artifacts":"updated_coverage_artifacts, sync_report","dispatcher-stack-tags":"cypress, coverage, sync","dispatcher-risk":"low","dispatcher-writes-files":true} |
[!IMPORTANT] All usage of this skill must be logged via the Skill Dispatcher to ensure audit logs and wallboard analytics are accurate:
./log-dispatch.cmd --skill <skill_name> --intent <intent> --model <model_name> --reason <reason>(or./log-dispatch.shon Linux)
Use this skill to keep planning artifacts aligned with reality after the suite changes.
Identify added, removed, renamed, or moved scenarios and reconcile them across:
.cy.ts files, titles, tags, or scenario IDs.Do not invent implementation links that you cannot verify.
Recalculate summary counts only after the underlying scenario rows are correct.
Flag drift explicitly when the plan claims coverage that the implementation cannot prove.
coverage_plan/*.md as the source of truth for planned scope.docs/tests/**/*.md as the narrative traceability layer when those files exist.