annatomkaannatomka/skills/playwright-mapping-update/SKILL.md

playwright-mapping-update

Skill1 starsChanged 6 months agoMITView on GitHub

Update the Playwright E2E test mapping file based on changes in a branch, typically used during PR creation to keep test mappings accurate

In this repository6 other files it gives its agents.
- mov-to-gifSkill
- playwright-failure-cluster-analysisSkill
- playwright-generateSkill
- playwright-impact-analysisSkill
- playwright-single-failure-diagnosisSkill
- tldrSkill

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 13 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Update the repository's E2E test mapping file based on local changes.
line 5
Distinctive:
when creating a PR
line 12
Distinctive:
when new features or tests are added
line 13
Distinctive:
when refactoring affects file paths or test coverage
line 14
Distinctive:
check if it exists in the detected E2E mapping file
line 37
Distinctive:
if not → candidate for new mapping
line 38
Distinctive:
check if it is referenced in the mapping
line 41
Distinctive:
if not → candidate for inclusion
line 42
Distinctive:
test file names and describe blocks
line 50
Distinctive:
Prefer consistency with existing mapping style.
line 52
Distinctive:
Do NOT rewrite the entire file.
line 62
Distinctive:
Do not apply changes automatically.
line 91
Distinctive:
prefer missing mapping over incorrect mapping
line 105
Very specific:
Use heuristics.md for inference logic.
line 107
Very specific:
Use output-template.md for formatting.
line 108

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Update the repository's E2E test mapping file based on local changes.

Your goal is to keep the mapping file accurate with minimal, reviewable changes.

When to use

This skill should be used:

when creating a PR
when new features or tests are added
when refactoring affects file paths or test coverage

Workflow

Discover the repository's E2E setup Inspect the repository before proposing mapping changes:
- E2E mapping files such as e2e-test-mapping.md, tests/e2e-test-mapping.md, e2e/e2e-test-mapping.md, __e2e__/e2e-test-mapping.md, or <detected-e2e-folder>/e2e-test-mapping.md
- Playwright config files such as playwright.config.ts, playwright.config.js, or playwright.config.mjs
- E2E folders such as e2e/, tests/e2e/, __e2e__/, playwright/, or folders referenced by Playwright config
- source/application folders used by the repository
Determine change scope Analyze local changes compared to the default branch, usually main or master.
Identify relevant changes Detect:
- new or modified source/application files
- new or modified E2E tests in the detected E2E folders
- deleted or renamed files
Analyze missing mappings
For each changed source file:
- check if it exists in the detected E2E mapping file
- if not → candidate for new mapping
For each changed test file:
- check if it is referenced in the mapping
- if not → candidate for inclusion
Infer mappings
Use:
- file path similarity
- feature/domain names
- existing mapping patterns
- test file names and describe blocks
Prefer consistency with existing mapping style.
Detect stale mappings
Identify:
- mappings pointing to deleted files
- outdated paths due to refactors
Generate minimal updates
Do NOT rewrite the entire file.
Only propose:
- additions
- removals
- updates
Respect existing structure
Maintain:
- section grouping
- formatting
- ordering
- naming conventions
Assign confidence
Use:
- HIGH → clear direct mapping
- MEDIUM → strong inference
- LOW → weak inference (optional suggestion)
Output a diff-style proposal

Show:

additions (+)
removals (-)
modifications (~)

Do not apply changes automatically.

Explain reasoning

For each proposed change:

what changed
why mapping is needed or incorrect
confidence level

Be conservative

If uncertain:

suggest but mark as LOW
do not overreach
prefer missing mapping over incorrect mapping

Use heuristics.md for inference logic. Use output-template.md for formatting.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free