How do I install the Pw Locator Fixer skill?

Run npx skillmds@latest add pramoddutta/pw-locator-fixer-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pw Locator Fixer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pw Locator Fixer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pw Locator Fixer free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Pw Locator Fixer?

PramodDutta (@pramoddutta) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pw Locator Fixer by pramoddutta — Agent Skill

Name: Pw Locator Fixer
Author: PramodDutta

Pw Locator Fixer

Scans a Playwright spec or Page Object for brittle locators and rewrites them to resilient ones. Use when an SDET says "fix these locators", "my selectors are flaky", "replace XPath with getByRole", "make these locators resilient", or pastes code full of nth-child/CSS-class/text selectors. Produces a before/ after rewrite map plus patched code — the engineer verifies each swap.

PramodDutta Updated Sep 21, 2026

File contents

PW Locator Fixer

You audit locators and propose resilient replacements the engineer must verify against the live DOM — a swap that reads well can still target the wrong node.

When to use

A spec/POM uses XPath, nth-child, CSS-class, or raw-text selectors.
Tests fail intermittently on element lookups.
Someone says "fix/harden/de-flake these locators".

Workflow

Scan the provided code and flag every brittle locator:
- XPath (//div[...]), page.locator('.some-class'), :nth-child, deep CSS descendant chains, index-based .nth(3), and unanchored text matches.
Rank the fix per element using the resilience ladder: getByRole (name) → getByLabel → getByPlaceholder → getByText (exact) → getByTestId. Reach for getByTestId when semantics are weak, not as the first choice.
Rewrite each locator, preserving intent. Where the original relied on position/text that maps to no stable attribute, mark // TODO: needs data-testid rather than inventing one.
Emit a rewrite map (before → after → why) so the change is reviewable.
Note residual risk — any swap you couldn't confirm without the real DOM.

Output shape

Rewrite map
  ✗ page.locator('//button[2]')          → ✓ getByRole('button', { name: 'Save' })
  ✗ page.locator('.err-msg')             → ✓ getByTestId('form-error')   // needs data-testid
  ✗ page.locator('tr:nth-child(3) td')   → ✓ getByRole('row', { name: /Order 1042/ })

// before
await page.locator('.login-form input.username').fill('ada');
// after
await page.getByLabel('Username').fill('ada');

Guardrails

These are proposed swaps the engineer must run and confirm — never assume the new locator resolves to the same element without checking the real DOM.
Never invent a data-testid or accessible name; if none exists, flag that the app needs one (// TODO: needs data-testid).
Prefer role/label semantics over testid; testid is the fallback, not the default.
Do not silently change behavior (strictness, count) — call out multi-match risks.

---name: pw-locator-fixer-2description: Scans a Playwright spec or Page Object for brittle locators and rewrites them to resilient ones. Use when an SDET says "fix these locators", "my selectors are flaky", "replace XPath with getByRole", "make these locators resilient", or pastes code full of nth-child/CSS-class/text selectors. Produces a before/ after rewrite map plus patched code — the engineer verifies each swap.license: MIT---# PW Locator FixerYou audit locators and **propose resilient replacements the engineer must verify**against the live DOM — a swap that reads well can still target the wrong node.## When to use- A spec/POM uses XPath, `nth-child`, CSS-class, or raw-text selectors.- Tests fail intermittently on element lookups.- Someone says "fix/harden/de-flake these locators".## Workflow1. **Scan** the provided code and flag every brittle locator: - XPath (`//div[...]`), `page.locator('.some-class')`, `:nth-child`, deep CSS descendant chains, index-based `.nth(3)`, and unanchored text matches.2. **Rank the fix** per element using the resilience ladder: `getByRole` (name) → `getByLabel` → `getByPlaceholder` → `getByText` (exact) → `getByTestId`. Reach for `getByTestId` when semantics are weak, not as the first choice.3. **Rewrite** each locator, preserving intent. Where the original relied on position/text that maps to no stable attribute, mark `// TODO: needs data-testid` rather than inventing one.4. **Emit a rewrite map** (before → after → why) so the change is reviewable.5. **Note residual risk** — any swap you couldn't confirm without the real DOM.## Output shape```Rewrite map ✗ page.locator('//button[2]') → ✓ getByRole('button', { name: 'Save' }) ✗ page.locator('.err-msg') → ✓ getByTestId('form-error') // needs data-testid ✗ page.locator('tr:nth-child(3) td') → ✓ getByRole('row', { name: /Order 1042/ })``````typescript// beforeawait page.locator('.login-form input.username').fill('ada');// afterawait page.getByLabel('Username').fill('ada');```## Guardrails- These are **proposed swaps the engineer must run and confirm** — never assume the new locator resolves to the same element without checking the real DOM.- Never invent a `data-testid` or accessible name; if none exists, flag that the app needs one (`// TODO: needs data-testid`).- Prefer role/label semantics over testid; testid is the fallback, not the default.- Do not silently change behavior (strictness, count) — call out multi-match risks.

Frequently asked questions