[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71K5N31WQBH7FJFNBM3TCPY":3,"skill-same:01M71K5N31WQBH7FJFNBM3TCPY":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M71K5N31WQBH7FJFNBM3TCPY","testing-strategy",null,"Design test strategies and test plans. Trigger with \"how should we test\", \"test strategy for\", \"write tests for\", \"test plan\", \"what tests do we need\", or when the user needs help with testing approaches, coverage, or test architecture.","mryfmo\u002Fdotfiles","mryfmo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11512262?v=4","01M71K2RDZFFQKYGMHMS5Y9PW1","01M71K2REKJ0WS61PNFQPTYP5T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Fengineering\u002Fskills\u002Ftesting-strategy\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"strategy","testing strategy","testing","plan","test","strategies","with","architecture","when","plans","design","tests","write tests","test strategy","trigger","test strategies","for","test plan","do","coverage","2026-11-10 10:12:30",false,"---\nname: testing-strategy\ndescription: Design test strategies and test plans. Trigger with \"how should we test\", \"test strategy for\", \"write tests for\", \"test plan\", \"what tests do we need\", or when the user needs help with testing approaches, coverage, or test architecture.\n---\n\n# Testing Strategy\n\nDesign effective testing strategies balancing coverage, speed, and maintenance.\n\n## Testing Pyramid\n\n```\n        \u002F  E2E  \\         Few, slow, high confidence\n       \u002F Integration \\     Some, medium speed\n      \u002F    Unit Tests  \\   Many, fast, focused\n```\n\n## Strategy by Component Type\n\n- **API endpoints**: Unit tests for business logic, integration tests for HTTP layer, contract tests for consumers\n- **Data pipelines**: Input validation, transformation correctness, idempotency tests\n- **Frontend**: Component tests, interaction tests, visual regression, accessibility\n- **Infrastructure**: Smoke tests, chaos engineering, load tests\n\n## What to Cover\n\nFocus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.\n\nSkip: trivial getters\u002Fsetters, framework code, one-off scripts.\n\n## Output\n\nProduce a test plan with: what to test, test type for each area, coverage targets, and example test cases. Identify gaps in existing coverage.\n","# Testing Strategy\n\nDesign effective testing strategies balancing coverage, speed, and maintenance.\n\n## Testing Pyramid\n\n```\n        \u002F  E2E  \\         Few, slow, high confidence\n       \u002F Integration \\     Some, medium speed\n      \u002F    Unit Tests  \\   Many, fast, focused\n```\n\n## Strategy by Component Type\n\n- **API endpoints**: Unit tests for business logic, integration tests for HTTP layer, contract tests for consumers\n- **Data pipelines**: Input validation, transformation correctness, idempotency tests\n- **Frontend**: Component tests, interaction tests, visual regression, accessibility\n- **Infrastructure**: Smoke tests, chaos engineering, load tests\n\n## What to Cover\n\nFocus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.\n\nSkip: trivial getters\u002Fsetters, framework code, one-off scripts.\n\n## Output\n\nProduce a test plan with: what to test, test type for each area, coverage targets, and example test cases. Identify gaps in existing coverage.\n",{"name":5,"description":7},"main","af601a97567f1f07e9337cad899506f601f419f1","tests\u002Ffixtures\u002Fkwp-upstream\u002Fengineering\u002Fskills\u002Ftesting-strategy","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fmryfmo","2026-11-13 12:53:52",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add mryfmo\u002Fdotfiles --skill testing-strategy",{"tool":60,"command":61},"bunx","bunx skills add mryfmo\u002Fdotfiles --skill testing-strategy",{"tool":63,"command":64},"pnpm","pnpm dlx skills add mryfmo\u002Fdotfiles --skill testing-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Fengineering\u002Fskills\u002Ftesting-strategy\u002FSKILL.md",true,[],[69,75,81,110,132,150],{"skillNo":70,"name":71,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":43},"01M71K61D634ATEV8NWTGGWNGS","x","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fponytail\u002Fskills\u002Fx\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":43},"01M71K605VRE3ABPN1MZHJNZ29","y","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fponytail\u002Fdocs\u002Fskills\u002Fy\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":43},"01M71K5Y3XX1PYZAWA7M5RG9VD","status-report","Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green\u002Fyellow\u002Fred status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Fstatus-report\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[93,94,95,96,97,98,99,100,29,101,102,103,39,104,105,106,31,107,108,109],"status report","report","status","tracker","health","generate","leadership","narrative","weekly","attention","green","project","writing","use","decisions","team","project health",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":43},"01M71K5VJAHGE1NH22BGBXP693","runbook","Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frunbook\u002FSKILL.md",[],[112,117,118,119,120,121,122,123,124,31,125,126,106,105,127,128,39,129,130,131],"task","update","name","run","process","operational","create","call","ops","Existing","knowledge","rollback","escalation","recurring","things",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":43},"01M71K5SJ0FT7KD82E7PJCGATX","risk-assessment","Identify, assess, and mitigate operational risks. Trigger with \"what are the risks\", \"risk assessment\", \"risk register\", \"what could go wrong\", or when the user is evaluating risks associated with a project, vendor, process, or decision.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frisk-assessment\u002FSKILL.md",[],[139,140,141,29,142,143,144,31,145,146,37,147,148,121,104,122,149],"risk assessment","assessment","risk","decision","user","Wrong","go","assess","risk register","vendor","register",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":43},"01M71K5PYD2A2BDM6KMZ8F01SV","change-request","Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Fchange-request\u002FSKILL.md",[],[157,158,159,106,29,160,161,162,163,164,165,31,166,167,168,169,170,39,171,141],"request","change request","change","communications","stakeholder communications","review","rollback plan","analysis","rollout","impact","change management","impact analysis","system","deployment","planning"]