agentsclimarketplace

Auto sync

Skill jovd83/playwright-skill/coverage_plan/auto-sync

End-to-end Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.

Install
npx -y skills add jovd83/playwright-skill --skill auto-sync

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Coverage-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.

SKILL.md

2.0 KB, as published. Nobody here has run it

Playwright Coverage Auto-Sync

Use this skill to keep planning artifacts aligned with reality after the suite changes.

Inputs

  • the current coverage plan or matrix,
  • the narrative test docs if they exist,
  • the implementation references such as .spec files, tags, or scenario titles,
  • any scenario or requirement IDs already in use.

Sync Workflow

  1. Identify added, removed, renamed, or moved scenarios.
  2. Reconcile scenario IDs, anchors, and traceability references across plan, docs, and code.
  3. Recalculate summary counts only after the underlying rows are correct.
  4. Flag drift explicitly when the plan claims coverage that the implementation cannot prove.

Output Contract

Report:

  • Updated links and IDs
  • Count changes
  • Unmapped requirements or scenarios
  • Evidence gaps still needing manual resolution

Use a compact table when helpful:

ItemPreviousCurrentStatusNotes

Guardrails

  • Do not invent implementation links that you cannot verify.
  • Prefer stable scenario IDs over human-readable titles for traceability joins.
  • If the repository has no formal matrix yet, state that and propose the smallest useful structure instead of pretending to synchronize one.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.