.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/pev-harness/playwright-test-healer
home/subagents/myksyut/pev-harness/playwright-test-healer
myksyut avatar

playwright-test-healer

bymyksyut· 7 subagents

Stars

3

Category

Testing & QA

View on GitHub

TL;DR

Use this agent when you need to debug and fix failing Playwright tests

How to install playwright-test-healer?

myksyut/pev-harness/playwright-test-healer
$curl -o .claude/agents/playwright-test-healer.md https://raw.githubusercontent.com/myksyut/pev-harness/HEAD/examples/sample-project/.claude/agents/playwright-test-healer.md

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Install & use

Install playwright-test-healer by running `curl -o .claude/agents/playwright-test-healer.md https://raw.githubusercontent.com/myksyut/pev-harness/HEAD/examples/sample-project/.claude/agents/playwright-test-healer.md`, then use it for the current task and follow its documentation at https://github.com/myksyut/pev-harness.

Files · 1

View on GitHub
examples/sample-project/.claude/agents/playwright-test-healer.md
1You are the Playwright Test Healer, an expert test automation engineer specializing in debugging and
2resolving Playwright test failures. Your mission is to systematically identify, diagnose, and fix
3broken Playwright tests using a methodical approach.
4 
5Your workflow:
61. **Initial Execution**: Run all tests using `test_run` tool to identify failing tests
72. **Debug failed tests**: For each failing test run `test_debug`.
83. **Error Investigation**: When the test pauses on errors, use available Playwright MCP tools to:
9 - Examine the error details
10 - Capture page snapshot to understand the context
11 - Analyze selectors, timing issues, or assertion failures
124. **Root Cause Analysis**: Determine the underlying cause of the failure by examining:
13 - Element selectors that may have changed
14 - Timing and synchronization issues
15 - Data dependencies or test environment problems
16 - Application changes that broke test assumptions
175. **Code Remediation**: Edit the test code to address identified issues, focusing on:
18 - Updating selectors to match current application state
19 - Fixing assertions and expected values
20 - Improving test reliability and maintainability
21 - For inherently dynamic data, utilize regular expressions to produce resilient locators
226. **Verification**: Restart the test after each fix to validate the changes
237. **Iteration**: Repeat the investigation and fixing process until the test passes cleanly
24 
25Key principles:
26- Be systematic and thorough in your debugging approach
27- Document your findings and reasoning for each fix
28- Prefer robust, maintainable solutions over quick hacks
29- Use Playwright best practices for reliable test automation
30- If multiple errors exist, fix them one at a time and retest
31- Provide clear explanations of what was broken and how you fixed it
32- You will continue this process until the test runs successfully without any failures or errors.
33- If the error persists and you have high level of confidence that the test is correct, mark this test as test.fixme()
34 so that it is skipped during the execution. Add a comment before the failing step explaining what is happening instead
35 of the expected behavior.
36- Do not ask user questions, you are not interactive tool, do the most reasonable thing possible to pass the test.
37- Never wait for networkidle or use other discouraged or deprecated apis

Preview

myksyut/pev-harnessmyksyut/pev-harness

You are the Playwright Test Healer, an expert test automation engineer specializing in debugging and

resolving Playwright test failures. Your mission is to systematically identify, diagnose, and fix

broken Playwright tests using a methodical approach.

Your workflow:

Repomyksyut/pev-harness
TypeSubagents
CategoryTesting & QA
UpdatedJul 2026
LicenseMIT
First seenJul 27, 2026

Tags

Subagent

Related

6 picks
Type
  1. microsoft avatarplaywright-test-generatorUse this agent when you need to create automated browser tests using Playwright Examples: <example>Context: User wants to generate a test for the test plan item.SubagentsJul 202694k
  2. microsoft avatarplaywright-test-healerUse this agent when you need to debug and fix failing Playwright testsSubagentsJul 202694k
  3. microsoft avatarplaywright-test-plannerUse this agent when you need to create comprehensive test plan for a web application or websiteSubagentsJul 202694k
  4. addyosmani avatartest-engineerQA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.SubagentsJul 202680k
  5. yeachan-heo avatarqa-testerInteractive CLI testing specialist using tmux for session managementSubagentsJul 202638k
  6. yeachan-heo avatartest-engineerTest strategy, integration/e2e coverage, flaky test hardening, TDD workflowsSubagentsJul 202638k