[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73AJKKFTXFSES1WXF97B885":3,"skill-same:01M73AJKKFTXFSES1WXF97B885":52},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M73AJKKFTXFSES1WXF97B885","review",null,"Review Playwright tests for quality. Use when user says \"review tests\", \"check test quality\", \"audit tests\", \"improve tests\", \"test code review\", or \"playwright best practices check\".","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-playwright-pro\u002Fskills\u002Freview\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"review\"\ndescription: >-\n  Review Playwright tests for quality. Use when user says \"review tests\",\n  \"check test quality\", \"audit tests\", \"improve tests\", \"test code review\",\n  or \"playwright best practices check\".\n---\n\n# Review Playwright Tests\n\nSystematically review Playwright test files for anti-patterns, missed best practices, and coverage gaps.\n\n## Input\n\n`$ARGUMENTS` can be:\n- A file path: review that specific test file\n- A directory: review all test files in the directory\n- Empty: review all tests in the project's `testDir`\n\n## Steps\n\n### 1. Gather Context\n\n- Read `playwright.config.ts` for project settings\n- List all `*.spec.ts` \u002F `*.spec.js` files in scope\n- If reviewing a single file, also check related page objects and fixtures\n\n### 2. Check Each File Against Anti-Patterns\n\nLoad `anti-patterns.md` from this skill directory. Check for all 20 anti-patterns.\n\n**Critical (must fix):**\n1. `waitForTimeout()` usage\n2. Non-web-first assertions (`expect(await ...)`)\n3. Hardcoded URLs instead of `baseURL`\n4. CSS\u002FXPath selectors when role-based exists\n5. Missing `await` on Playwright calls\n6. Shared mutable state between tests\n7. Test execution order dependencies\n\n**Warning (should fix):**\n8. Tests longer than 50 lines (consider splitting)\n9. Magic strings without named constants\n10. Missing error\u002Fedge case tests\n11. `page.evaluate()` for things locators can do\n12. Nested `test.describe()` more than 2 levels deep\n13. Generic test names (\"should work\", \"test 1\")\n\n**Info (consider):**\n14. No page objects for pages with 5+ locators\n15. Inline test data instead of factory\u002Ffixture\n16. Missing accessibility assertions\n17. No visual regression tests for UI-heavy pages\n18. Console error assertions not checked\n19. Network idle waits instead of specific assertions\n20. Missing `test.describe()` grouping\n\n### 3. Score Each File\n\nRate 1-10 based on:\n- **9-10**: Production-ready, follows all golden rules\n- **7-8**: Good, minor improvements possible\n- **5-6**: Functional but has anti-patterns\n- **3-4**: Significant issues, likely flaky\n- **1-2**: Needs rewrite\n\n### 4. Generate Review Report\n\nFor each file:\n```\n## \u003Cfilename> — Score: X\u002F10\n\n### Critical\n- Line 15: `waitForTimeout(2000)` → use `expect(locator).toBeVisible()`\n- Line 28: CSS selector `.btn-submit` → `getByRole('button', { name: \"submit\" })`\n\n### Warning\n- Line 42: Test name \"test login\" → \"should redirect to dashboard after login\"\n\n### Suggestions\n- Consider adding error case: what happens with invalid credentials?\n```\n\n### 5. For Project-Wide Review\n\nIf reviewing an entire test suite:\n- Spawn sub-agents per file for parallel review (up to 5 concurrent)\n- Or use `\u002Fbatch` for very large suites\n- Aggregate results into a summary table\n\n### 6. Offer Fixes\n\nFor each critical issue, provide the corrected code. Ask user: \"Apply these fixes? [Yes\u002FNo]\"\n\nIf yes, apply all fixes using `Edit` tool.\n\n## Output\n\n- File-by-file review with scores\n- Summary: total files, average score, critical issue count\n- Actionable fix list\n- Coverage gaps identified (pages\u002Ffeatures with no tests)\n","# Review Playwright Tests\n\nSystematically review Playwright test files for anti-patterns, missed best practices, and coverage gaps.\n\n## Input\n\n`$ARGUMENTS` can be:\n- A file path: review that specific test file\n- A directory: review all test files in the directory\n- Empty: review all tests in the project's `testDir`\n\n## Steps\n\n### 1. Gather Context\n\n- Read `playwright.config.ts` for project settings\n- List all `*.spec.ts` \u002F `*.spec.js` files in scope\n- If reviewing a single file, also check related page objects and fixtures\n\n### 2. Check Each File Against Anti-Patterns\n\nLoad `anti-patterns.md` from this skill directory. Check for all 20 anti-patterns.\n\n**Critical (must fix):**\n1. `waitForTimeout()` usage\n2. Non-web-first assertions (`expect(await ...)`)\n3. Hardcoded URLs instead of `baseURL`\n4. CSS\u002FXPath selectors when role-based exists\n5. Missing `await` on Playwright calls\n6. Shared mutable state between tests\n7. Test execution order dependencies\n\n**Warning (should fix):**\n8. Tests longer than 50 lines (consider splitting)\n9. Magic strings without named constants\n10. Missing error\u002Fedge case tests\n11. `page.evaluate()` for things locators can do\n12. Nested `test.describe()` more than 2 levels deep\n13. Generic test names (\"should work\", \"test 1\")\n\n**Info (consider):**\n14. No page objects for pages with 5+ locators\n15. Inline test data instead of factory\u002Ffixture\n16. Missing accessibility assertions\n17. No visual regression tests for UI-heavy pages\n18. Console error assertions not checked\n19. Network idle waits instead of specific assertions\n20. Missing `test.describe()` grouping\n\n### 3. Score Each File\n\nRate 1-10 based on:\n- **9-10**: Production-ready, follows all golden rules\n- **7-8**: Good, minor improvements possible\n- **5-6**: Functional but has anti-patterns\n- **3-4**: Significant issues, likely flaky\n- **1-2**: Needs rewrite\n\n### 4. Generate Review Report\n\nFor each file:\n```\n## \u003Cfilename> — Score: X\u002F10\n\n### Critical\n- Line 15: `waitForTimeout(2000)` → use `expect(locator).toBeVisible()`\n- Line 28: CSS selector `.btn-submit` → `getByRole('button', { name: \"submit\" })`\n\n### Warning\n- Line 42: Test name \"test login\" → \"should redirect to dashboard after login\"\n\n### Suggestions\n- Consider adding error case: what happens with invalid credentials?\n```\n\n### 5. For Project-Wide Review\n\nIf reviewing an entire test suite:\n- Spawn sub-agents per file for parallel review (up to 5 concurrent)\n- Or use `\u002Fbatch` for very large suites\n- Aggregate results into a summary table\n\n### 6. Offer Fixes\n\nFor each critical issue, provide the corrected code. Ask user: \"Apply these fixes? [Yes\u002FNo]\"\n\nIf yes, apply all fixes using `Edit` tool.\n\n## Output\n\n- File-by-file review with scores\n- Summary: total files, average score, critical issue count\n- Actionable fix list\n- Coverage gaps identified (pages\u002Ffeatures with no tests)\n",{"name":5,"description":7},"main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fnginity-playwright-pro\u002Fskills\u002Freview","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kalash33\u002Fkstack --skill review",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill review",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-playwright-pro\u002Fskills\u002Freview\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"anti-patterns.md","REFERENCE","参考文档",4294,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-playwright-pro\u002Fskills\u002Freview\u002Fanti-patterns.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]