[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DS0VMZVCEKPPYN4CGXYPFS":3,"skill-same:01M6DS0VMZVCEKPPYN4CGXYPFS":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6DS0VMZVCEKPPYN4CGXYPFS","fix",null,"Fix failing or flaky Playwright tests. Use when user says \"fix test\", \"flaky test\", \"test failing\", \"debug test\", \"test broken\", \"test passes sometimes\", or \"intermittent failure\".","zhangzhang-111-i\u002Fclaude-skills111","zhangzhang-111-i","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F251344927?v=4","01M6DRBP4NCM1ZCHTT0FW0SQHD","lixiying","01M6DRBPAMFDJSGQ69XPK9KM9J",3,"MIT","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Ffix\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31],"playwright","test","debug","debug test","broken","user","use","tests","2026-11-10 10:12:30",false,"---\nname: \"fix\"\ndescription: >-\n  Fix failing or flaky Playwright tests. Use when user says \"fix test\",\n  \"flaky test\", \"test failing\", \"debug test\", \"test broken\", \"test passes\n  sometimes\", or \"intermittent failure\".\n---\n\n# Fix Failing or Flaky Tests\n\nDiagnose and fix a Playwright test that fails or passes intermittently using a systematic taxonomy.\n\n## Input\n\n`$ARGUMENTS` contains:\n- A test file path: `e2e\u002Flogin.spec.ts`\n- A test name: \"\"should redirect after login\"`\n- A description: `\"the checkout test fails in CI but passes locally\"`\n\n## Steps\n\n### 1. Reproduce the Failure\n\nRun the test to capture the error:\n\n```bash\nnpx playwright test \u003Cfile> --reporter=list\n```\n\nIf the test passes, it's likely flaky. Run burn-in:\n\n```bash\nnpx playwright test \u003Cfile> --repeat-each=10 --reporter=list\n```\n\nIf it still passes, try with parallel workers:\n\n```bash\nnpx playwright test --fully-parallel --workers=4 --repeat-each=5\n```\n\n### 2. Capture Trace\n\nRun with full tracing:\n\n```bash\nnpx playwright test \u003Cfile> --trace=on --retries=0\n```\n\nRead the trace output. Use `\u002Fdebug` to analyze trace files if available.\n\n### 3. Categorize the Failure\n\nLoad `flaky-taxonomy.md` from this skill directory.\n\nEvery failing test falls into one of four categories:\n\n| Category | Symptom | Diagnosis |\n|---|---|---|\n| **Timing\u002FAsync** | Fails intermittently everywhere | `--repeat-each=20` reproduces locally |\n| **Test Isolation** | Fails in suite, passes alone | `--workers=1 --grep \"test name\"` passes |\n| **Environment** | Fails in CI, passes locally | Compare CI vs local screenshots\u002Ftraces |\n| **Infrastructure** | Random, no pattern | Error references browser internals |\n\n### 4. Apply Targeted Fix\n\n**Timing\u002FAsync:**\n- Replace `waitForTimeout()` with web-first assertions\n- Add `await` to missing Playwright calls\n- Wait for specific network responses before asserting\n- Use `toBeVisible()` before interacting with elements\n\n**Test Isolation:**\n- Remove shared mutable state between tests\n- Create test data per-test via API or fixtures\n- Use unique identifiers (timestamps, random strings) for test data\n- Check for database state leaks\n\n**Environment:**\n- Match viewport sizes between local and CI\n- Account for font rendering differences in screenshots\n- Use `docker` locally to match CI environment\n- Check for timezone-dependent assertions\n\n**Infrastructure:**\n- Increase timeout for slow CI runners\n- Add retries in CI config (`retries: 2`)\n- Check for browser OOM (reduce parallel workers)\n- Ensure browser dependencies are installed\n\n### 5. Verify the Fix\n\nRun the test 10 times to confirm stability:\n\n```bash\nnpx playwright test \u003Cfile> --repeat-each=10 --reporter=list\n```\n\nAll 10 must pass. If any fail, go back to step 3.\n\n### 6. Prevent Recurrence\n\nSuggest:\n- Add to CI with `retries: 2` if not already\n- Enable `trace: 'on-first-retry'` in config\n- Add the fix pattern to project's test conventions doc\n\n## Output\n\n- Root cause category and specific issue\n- The fix applied (with diff)\n- Verification result (10\u002F10 passes)\n- Prevention recommendation\n","# Fix Failing or Flaky Tests\n\nDiagnose and fix a Playwright test that fails or passes intermittently using a systematic taxonomy.\n\n## Input\n\n`$ARGUMENTS` contains:\n- A test file path: `e2e\u002Flogin.spec.ts`\n- A test name: \"\"should redirect after login\"`\n- A description: `\"the checkout test fails in CI but passes locally\"`\n\n## Steps\n\n### 1. Reproduce the Failure\n\nRun the test to capture the error:\n\n```bash\nnpx playwright test \u003Cfile> --reporter=list\n```\n\nIf the test passes, it's likely flaky. Run burn-in:\n\n```bash\nnpx playwright test \u003Cfile> --repeat-each=10 --reporter=list\n```\n\nIf it still passes, try with parallel workers:\n\n```bash\nnpx playwright test --fully-parallel --workers=4 --repeat-each=5\n```\n\n### 2. Capture Trace\n\nRun with full tracing:\n\n```bash\nnpx playwright test \u003Cfile> --trace=on --retries=0\n```\n\nRead the trace output. Use `\u002Fdebug` to analyze trace files if available.\n\n### 3. Categorize the Failure\n\nLoad `flaky-taxonomy.md` from this skill directory.\n\nEvery failing test falls into one of four categories:\n\n| Category | Symptom | Diagnosis |\n|---|---|---|\n| **Timing\u002FAsync** | Fails intermittently everywhere | `--repeat-each=20` reproduces locally |\n| **Test Isolation** | Fails in suite, passes alone | `--workers=1 --grep \"test name\"` passes |\n| **Environment** | Fails in CI, passes locally | Compare CI vs local screenshots\u002Ftraces |\n| **Infrastructure** | Random, no pattern | Error references browser internals |\n\n### 4. Apply Targeted Fix\n\n**Timing\u002FAsync:**\n- Replace `waitForTimeout()` with web-first assertions\n- Add `await` to missing Playwright calls\n- Wait for specific network responses before asserting\n- Use `toBeVisible()` before interacting with elements\n\n**Test Isolation:**\n- Remove shared mutable state between tests\n- Create test data per-test via API or fixtures\n- Use unique identifiers (timestamps, random strings) for test data\n- Check for database state leaks\n\n**Environment:**\n- Match viewport sizes between local and CI\n- Account for font rendering differences in screenshots\n- Use `docker` locally to match CI environment\n- Check for timezone-dependent assertions\n\n**Infrastructure:**\n- Increase timeout for slow CI runners\n- Add retries in CI config (`retries: 2`)\n- Check for browser OOM (reduce parallel workers)\n- Ensure browser dependencies are installed\n\n### 5. Verify the Fix\n\nRun the test 10 times to confirm stability:\n\n```bash\nnpx playwright test \u003Cfile> --repeat-each=10 --reporter=list\n```\n\nAll 10 must pass. If any fail, go back to step 3.\n\n### 6. Prevent Recurrence\n\nSuggest:\n- Add to CI with `retries: 2` if not already\n- Enable `trace: 'on-first-retry'` in config\n- Add the fix pattern to project's test conventions doc\n\n## Output\n\n- Root cause category and specific issue\n- The fix applied (with diff)\n- Verification result (10\u002F10 passes)\n- Prevention recommendation\n",{"name":5,"description":7},"main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","engineering-team\u002Fplaywright-pro\u002Fskills\u002Ffix",0,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i","2026-03-13 21:49:18",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill fix",{"tool":50,"command":51},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill fix",{"tool":53,"command":54},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill fix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Ffix\u002FSKILL.md",true,[58,64,70,74,78,82],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},".security-scan-passed","OTHER","其他",181,"https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fdaymade\u002Fgithub-contributor\u002F.security-scan-passed",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"flaky-taxonomy.md","REFERENCE","参考文档",3496,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Ffix\u002Fflaky-taxonomy.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fcommunication_templates.md",5410,"https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fdaymade\u002Fgithub-contributor\u002Freferences\u002Fcommunication_templates.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fhigh_quality_pr_case_study.md",8187,"https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fdaymade\u002Fgithub-contributor\u002Freferences\u002Fhigh_quality_pr_case_study.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fpr_checklist.md",7011,"https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fdaymade\u002Fgithub-contributor\u002Freferences\u002Fpr_checklist.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fproject_evaluation.md",3337,"https:\u002F\u002Fgithub.com\u002FHuuBar\u002Fskill-routing-experiment\u002Fblob\u002Fmain\u002Funified_skills\u002Fdaymade\u002Fgithub-contributor\u002Freferences\u002Fproject_evaluation.md",[87,112,138,167,187,210],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":32},"01M6DSNYM8PZKEXGYMRX53PVPH","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[94,95,96,97,98,99,100,101,102,103,104,29,30,105,106,107,108,109,110,111],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","analysis","risk matrix","Market","device","control","iso","medical","iso 14971",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":32},"01M6DSNSRBGVZWS23TK0ZQ52QC","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,110,137],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","plan","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":152,"publishedAt":32},"01M6DSNN7GNR2HZE66S4D31EP8","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[144,147],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[153,154,155,156,157,158,122,159,160,161,162,163,30,120,164,165,166,108,109,110],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":176,"publishedAt":32},"01M6DSNE5PQM106PM4EDGPBWGZ","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[173],{"categoryNo":174,"categoryName":175,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000037","律师与法务",[177,154,156,178,179,180,181,161,182,162,96,183,120,184,185,186,109],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":197,"publishedAt":32},"01M6DSN7MYXB6X42TB1GH2TNSB","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[193,196],{"categoryNo":194,"categoryName":195,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":174,"categoryName":175,"taxonomyType":150,"taxonomyTypeDesc":151},[122,198,154,156,199,200,159,103,201,162,202,203,30,204,205,206,110,207,208,209],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":216,"publishedAt":32},"01M6DSN3R749H3R20K15QE8X8W","qms-audit-expert","ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use for internal audit planning, audit execution, finding classification, external audit preparation, or audit program management.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fqms-audit-expert\u002FSKILL.md",[],[159,217,218,125,219,220,221,222,96,30,223,107,109,110],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]