How do I install the Pw Locator Fixer skill?

Run npx skillmds@latest add pramoddutta/pw-locator-fixer-3 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 22, 2026

File contents

PW Locator Fixer

This app is data-test driven

TTACart exposes data-test on everything that matters, so the target here is [data-test="..."], not getByRole. Check src/pages/*.ts for the attribute that already covers the element before inventing a new strategy.

Priority order

[data-test="..."], the app's own contract.
getByRole(...) with an accessible name, for anything genuinely lacking a test id.
getByLabel / getByPlaceholder, form controls only.
Everything else is a finding, not a solution.

Rewrite on sight: XPath, nth-child, chained CSS classes, index-based .nth(n) standing in for identity, and text selectors that break on copy changes.

Framework rules that outrank locator style

A locator belongs in a Page Object, never in a spec. Moving a selector out of a spec into the POM counts as a fix even when the selector itself was fine.
Locators are private readonly fields assigned in the constructor. Dynamic ones are private methods returning Locator, as in InventoryPage.addBtn(id).
Actions go through this.el.*. A locator swap that leaves a raw .click() behind is half a fix.

Output shape

Report a table first, patch second:

File	Before	After	Why
`src/pages/CartPage.ts:47`	`.cart_item:nth-child(2)`	`[data-test="inventory-item"]`	index broke when sort order changed

Verify

npx tsc --noEmit -p tsconfig.json
npx playwright test        # the swap must be proven, not assumed

A locator change that is not re-run is not a fix. Run the specs that touch the page you edited.

---name: pw-locator-fixer-3description: 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 Fixer## This app is data-test drivenTTACart exposes `data-test` on everything that matters, so the target here is`[data-test="..."]`, not `getByRole`. Check `src/pages/*.ts` for the attribute that already coversthe element before inventing a new strategy.## Priority order1. `[data-test="..."]`, the app's own contract.2. `getByRole(...)` with an accessible name, for anything genuinely lacking a test id.3. `getByLabel` / `getByPlaceholder`, form controls only.4. Everything else is a finding, not a solution.Rewrite on sight: XPath, `nth-child`, chained CSS classes, index-based `.nth(n)` standing in foridentity, and text selectors that break on copy changes.## Framework rules that outrank locator style- A locator belongs in a Page Object, never in a spec. Moving a selector out of a spec into the POM counts as a fix even when the selector itself was fine.- Locators are `private readonly` fields assigned in the constructor. Dynamic ones are private methods returning `Locator`, as in `InventoryPage.addBtn(id)`.- Actions go through `this.el.*`. A locator swap that leaves a raw `.click()` behind is half a fix.## Output shapeReport a table first, patch second:| File | Before | After | Why ||---|---|---|---|| `src/pages/CartPage.ts:47` | `.cart_item:nth-child(2)` | `[data-test="inventory-item"]` | index broke when sort order changed |## Verify```bashnpx tsc --noEmit -p tsconfig.jsonnpx playwright test # the swap must be proven, not assumed```A locator change that is not re-run is not a fix. Run the specs that touch the page you edited.

Frequently asked questions