[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FXFDZ0J5NEE08R7QZPPR5N":3,"skill-same:01M6FXFDZ0J5NEE08R7QZPPR5N":65},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6FXFDZ0J5NEE08R7QZPPR5N","test-fixing",null,"Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fother\u002Ftest-fixing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36],"test","test fixing","run tests","run","user","fix","use","test suite","community","grouping","tests","error","requests","2026-11-10 10:12:30",false,"---\nname: test-fixing\ndescription: \"Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...\"\nrisk: unknown\nsource: community\n---\n\n# Test Fixing\n\nSystematically identify and fix all failing tests using smart grouping strategies.\n\n## When to Use\n\n- Explicitly asks to fix tests (\"fix these tests\", \"make tests pass\")\n- Reports test failures (\"tests are failing\", \"test suite is broken\")\n- Completes implementation and wants tests passing\n- Mentions CI\u002FCD failures due to tests\n\n## Systematic Approach\n\n### 1. Initial Test Run\n\nRun `make test` to identify all failing tests.\n\nAnalyze output for:\n\n- Total number of failures\n- Error types and patterns\n- Affected modules\u002Ffiles\n\n### 2. Smart Error Grouping\n\nGroup similar failures by:\n\n- **Error type**: ImportError, AttributeError, AssertionError, etc.\n- **Module\u002Ffile**: Same file causing multiple test failure\n- **Root cause**: Missing dependencies, API changes, refactoring impacts\n\nPrioritize groups by:\n\n- Number of affected tests (highest impact first)\n- Dependency order (fix infrastructure before functionality)\n\n### 3. Systematic Fixing Process\n\nFor each group (starting with highest impact):\n\n1. **Identify root cause**\n\n   - Read relevant code\n   - Check recent changes with `git diff`\n   - Understand the error pattern\n\n2. **Implement fix**\n\n   - Use Edit tool for code changes\n   - Follow project conventions (see CLAUDE.md)\n   - Make minimal, focused changes\n\n3. **Verify fix**\n\n   - Run subset of tests for this group\n   - Use pytest markers or file patterns:\n     ```bash\n     uv run pytest tests\u002Fpath\u002Fto\u002Ftest_file.py -v\n     uv run pytest -k \"pattern\" -v\n     ```\n   - Ensure group passes before moving on\n\n4. **Move to next group**\n\n### 4. Fix Order Strategy\n\n**Infrastructure first:**\n\n- Import errors\n- Missing dependencies\n- Configuration issues\n\n**Then API changes:**\n\n- Function signature changes\n- Module reorganization\n- Renamed variables\u002Ffunctions\n\n**Finally, logic issues:**\n\n- Assertion failures\n- Business logic bugs\n- Edge case handling\n\n### 5. Final Verification\n\nAfter all groups fixed:\n\n- Run complete test suite: `make test`\n- Verify no regressions\n- Check test coverage remains intact\n\n## Best Practices\n\n- Fix one group at a time\n- Run focused tests after each fix\n- Use `git diff` to understand recent changes\n- Look for patterns in failures\n- Don't move to next group until current passes\n- Keep changes minimal and focused\n\n## Example Workflow\n\nUser: \"The tests are failing after my refactor\"\n\n1. Run `make test` → 15 failures identified\n2. Group errors:\n   - 8 ImportErrors (module renamed)\n   - 5 AttributeErrors (function signature changed)\n   - 2 AssertionErrors (logic bugs)\n3. Fix ImportErrors first → Run subset → Verify\n4. Fix AttributeErrors → Run subset → Verify\n5. Fix AssertionErrors → Run subset → Verify\n6. Run full suite → All pass ✓\n","# Test Fixing\n\nSystematically identify and fix all failing tests using smart grouping strategies.\n\n## When to Use\n\n- Explicitly asks to fix tests (\"fix these tests\", \"make tests pass\")\n- Reports test failures (\"tests are failing\", \"test suite is broken\")\n- Completes implementation and wants tests passing\n- Mentions CI\u002FCD failures due to tests\n\n## Systematic Approach\n\n### 1. Initial Test Run\n\nRun `make test` to identify all failing tests.\n\nAnalyze output for:\n\n- Total number of failures\n- Error types and patterns\n- Affected modules\u002Ffiles\n\n### 2. Smart Error Grouping\n\nGroup similar failures by:\n\n- **Error type**: ImportError, AttributeError, AssertionError, etc.\n- **Module\u002Ffile**: Same file causing multiple test failure\n- **Root cause**: Missing dependencies, API changes, refactoring impacts\n\nPrioritize groups by:\n\n- Number of affected tests (highest impact first)\n- Dependency order (fix infrastructure before functionality)\n\n### 3. Systematic Fixing Process\n\nFor each group (starting with highest impact):\n\n1. **Identify root cause**\n\n   - Read relevant code\n   - Check recent changes with `git diff`\n   - Understand the error pattern\n\n2. **Implement fix**\n\n   - Use Edit tool for code changes\n   - Follow project conventions (see CLAUDE.md)\n   - Make minimal, focused changes\n\n3. **Verify fix**\n\n   - Run subset of tests for this group\n   - Use pytest markers or file patterns:\n     ```bash\n     uv run pytest tests\u002Fpath\u002Fto\u002Ftest_file.py -v\n     uv run pytest -k \"pattern\" -v\n     ```\n   - Ensure group passes before moving on\n\n4. **Move to next group**\n\n### 4. Fix Order Strategy\n\n**Infrastructure first:**\n\n- Import errors\n- Missing dependencies\n- Configuration issues\n\n**Then API changes:**\n\n- Function signature changes\n- Module reorganization\n- Renamed variables\u002Ffunctions\n\n**Finally, logic issues:**\n\n- Assertion failures\n- Business logic bugs\n- Edge case handling\n\n### 5. Final Verification\n\nAfter all groups fixed:\n\n- Run complete test suite: `make test`\n- Verify no regressions\n- Check test coverage remains intact\n\n## Best Practices\n\n- Fix one group at a time\n- Run focused tests after each fix\n- Use `git diff` to understand recent changes\n- Look for patterns in failures\n- Don't move to next group until current passes\n- Keep changes minimal and focused\n\n## Example Workflow\n\nUser: \"The tests are failing after my refactor\"\n\n1. Run `make test` → 15 failures identified\n2. Group errors:\n   - 8 ImportErrors (module renamed)\n   - 5 AttributeErrors (function signature changed)\n   - 2 AssertionErrors (logic bugs)\n3. Fix ImportErrors first → Run subset → Verify\n4. Fix AttributeErrors → Run subset → Verify\n5. Fix AssertionErrors → Run subset → Verify\n6. Run full suite → All pass ✓\n",{"name":5,"risk":42,"source":32,"description":7},"unknown","master","dff58085da947e81e8418c922055644bf0082b1b","other\u002Ftest-fixing","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add reikiplanet\u002Fdaoskills --skill test-fixing",{"tool":57,"command":58},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill test-fixing",{"tool":60,"command":61},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill test-fixing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fother\u002Ftest-fixing\u002FSKILL.md",true,[],[66,92,104,118,138,161],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":37},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[73,74,75,76,77,78,32,79,80,81,82,83,84,85,86,87,88,89,90,91],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":37},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[99,100,90,101,102,32,80,81,82,76,103,77],"ar","vr ar","interaction","requirements","performance",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":37},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[106,111,112,113,114,115,32,30,82,116,117,76],"project scaffolding","From Scratch","tech","project","scaffolding","projects","applications",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":37},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[125,126,127,128,129,32,130,131,132,133,30,134,135,136,137],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"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":144,"publishedAt":37},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[145,146,147,148,149,150,151,152,32,82,76,153,77,154,155,156,157,158,159,160],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":37},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[168,169,170,171,172,173,174,175,158,30,176,177,178,32,179,180,181,155,182,183],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]