[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DS0QS6Z179YC53SPS1AEXB":3,"skill-same:01M6DS0QS6Z179YC53SPS1AEXB":66},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M6DS0QS6Z179YC53SPS1AEXB","coverage",null,"Analyze test coverage gaps. Use when user says \"test coverage\", \"what's not tested\", \"coverage gaps\", \"missing tests\", \"coverage report\", or \"what needs testing\".","zhangzhang-111-i\u002Fclaude-skills111","zhangzhang-111-i","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F251344927?v=4","01M6DRBP4NCM1ZCHTT0FW0SQHD","lixiying","01M6DRBPAMFDJSGQ69XPK9KM9J",4,"MIT","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Fcoverage\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33],"testing","test","coverage gaps","report","analyze","user","use","test coverage","tests","missing","2026-11-10 10:12:30",false,"---\nname: \"coverage\"\ndescription: >-\n  Analyze test coverage gaps. Use when user says \"test coverage\",\n  \"what's not tested\", \"coverage gaps\", \"missing tests\", \"coverage report\",\n  or \"what needs testing\".\n---\n\n# Analyze Test Coverage Gaps\n\nMap all testable surfaces in the application and identify what's tested vs. what's missing.\n\n## Steps\n\n### 1. Map Application Surface\n\nUse the `Explore` subagent to catalog:\n\n**Routes\u002FPages:**\n- Scan route definitions (Next.js `app\u002F`, React Router config, Vue Router, etc.)\n- List all user-facing pages with their paths\n\n**Components:**\n- Identify interactive components (forms, modals, dropdowns, tables)\n- Note components with complex state logic\n\n**API Endpoints:**\n- Scan API route files or backend controllers\n- List all endpoints with their methods\n\n**User Flows:**\n- Identify critical paths: auth, checkout, onboarding, core features\n- Map multi-step workflows\n\n### 2. Map Existing Tests\n\nScan all `*.spec.ts` \u002F `*.spec.js` files:\n\n- Extract which pages\u002Froutes are covered (by `page.goto()` calls)\n- Extract which components are tested (by locator usage)\n- Extract which API endpoints are mocked or hit\n- Count tests per area\n\n### 3. Generate Coverage Matrix\n\n```\n## Coverage Matrix\n\n| Area | Route | Tests | Status |\n|---|---|---|---|\n| Auth | \u002Flogin | 5 | ✅ Covered |\n| Auth | \u002Fregister | 0 | ❌ Missing |\n| Auth | \u002Fforgot-password | 0 | ❌ Missing |\n| Dashboard | \u002Fdashboard | 3 | ⚠️ Partial (no error states) |\n| Settings | \u002Fsettings | 0 | ❌ Missing |\n| Checkout | \u002Fcheckout | 8 | ✅ Covered |\n```\n\n### 4. Prioritize Gaps\n\nRank uncovered areas by business impact:\n\n1. **Critical** — auth, payment, core features → test first\n2. **High** — user-facing CRUD, search, navigation\n3. **Medium** — settings, preferences, edge cases\n4. **Low** — static pages, about, terms\n\n### 5. Suggest Test Plan\n\nFor each gap, recommend:\n- Number of tests needed\n- Which template from `templates\u002F` to use\n- Estimated effort (quick\u002Fmedium\u002Fcomplex)\n\n```\n## Recommended Test Plan\n\n### Priority 1: Critical\n1. \u002Fregister (4 tests) — use auth\u002Fregistration template — quick\n2. \u002Fforgot-password (3 tests) — use auth\u002Fpassword-reset template — quick\n\n### Priority 2: High\n3. \u002Fsettings (4 tests) — use settings\u002F templates — medium\n4. Dashboard error states (2 tests) — use dashboard\u002Fdata-loading template — quick\n```\n\n### 6. Auto-Generate (Optional)\n\nAsk user: \"Generate tests for the top N gaps? [Yes\u002FNo\u002FPick specific]\"\n\nIf yes, invoke `\u002Fpw:generate` for each gap with the recommended template.\n\n## Output\n\n- Coverage matrix (table format)\n- Coverage percentage estimate\n- Prioritized gap list with effort estimates\n- Option to auto-generate missing tests\n","# Analyze Test Coverage Gaps\n\nMap all testable surfaces in the application and identify what's tested vs. what's missing.\n\n## Steps\n\n### 1. Map Application Surface\n\nUse the `Explore` subagent to catalog:\n\n**Routes\u002FPages:**\n- Scan route definitions (Next.js `app\u002F`, React Router config, Vue Router, etc.)\n- List all user-facing pages with their paths\n\n**Components:**\n- Identify interactive components (forms, modals, dropdowns, tables)\n- Note components with complex state logic\n\n**API Endpoints:**\n- Scan API route files or backend controllers\n- List all endpoints with their methods\n\n**User Flows:**\n- Identify critical paths: auth, checkout, onboarding, core features\n- Map multi-step workflows\n\n### 2. Map Existing Tests\n\nScan all `*.spec.ts` \u002F `*.spec.js` files:\n\n- Extract which pages\u002Froutes are covered (by `page.goto()` calls)\n- Extract which components are tested (by locator usage)\n- Extract which API endpoints are mocked or hit\n- Count tests per area\n\n### 3. Generate Coverage Matrix\n\n```\n## Coverage Matrix\n\n| Area | Route | Tests | Status |\n|---|---|---|---|\n| Auth | \u002Flogin | 5 | ✅ Covered |\n| Auth | \u002Fregister | 0 | ❌ Missing |\n| Auth | \u002Fforgot-password | 0 | ❌ Missing |\n| Dashboard | \u002Fdashboard | 3 | ⚠️ Partial (no error states) |\n| Settings | \u002Fsettings | 0 | ❌ Missing |\n| Checkout | \u002Fcheckout | 8 | ✅ Covered |\n```\n\n### 4. Prioritize Gaps\n\nRank uncovered areas by business impact:\n\n1. **Critical** — auth, payment, core features → test first\n2. **High** — user-facing CRUD, search, navigation\n3. **Medium** — settings, preferences, edge cases\n4. **Low** — static pages, about, terms\n\n### 5. Suggest Test Plan\n\nFor each gap, recommend:\n- Number of tests needed\n- Which template from `templates\u002F` to use\n- Estimated effort (quick\u002Fmedium\u002Fcomplex)\n\n```\n## Recommended Test Plan\n\n### Priority 1: Critical\n1. \u002Fregister (4 tests) — use auth\u002Fregistration template — quick\n2. \u002Fforgot-password (3 tests) — use auth\u002Fpassword-reset template — quick\n\n### Priority 2: High\n3. \u002Fsettings (4 tests) — use settings\u002F templates — medium\n4. Dashboard error states (2 tests) — use dashboard\u002Fdata-loading template — quick\n```\n\n### 6. Auto-Generate (Optional)\n\nAsk user: \"Generate tests for the top N gaps? [Yes\u002FNo\u002FPick specific]\"\n\nIf yes, invoke `\u002Fpw:generate` for each gap with the recommended template.\n\n## Output\n\n- Coverage matrix (table format)\n- Coverage percentage estimate\n- Prioritized gap list with effort estimates\n- Option to auto-generate missing tests\n",{"name":5,"description":7},"main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","engineering-team\u002Fplaywright-pro\u002Fskills\u002Fcoverage",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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill coverage",{"tool":52,"command":53},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill coverage",{"tool":55,"command":56},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill coverage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Fcoverage\u002FSKILL.md",true,[60],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"index.json","REFERENCE","参考文档",595,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Flinux-fs-squashfs-unpack-analyze\u002Findex.json",[67,92,118,147,167,190],{"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":34},"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",[],[74,75,76,77,78,79,80,81,82,83,84,29,30,85,86,87,88,89,90,91],"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":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":34},"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",[],[99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,90,117],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","plan","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"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":132,"publishedAt":34},"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",[124,127],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[133,134,135,136,137,138,102,139,140,141,142,143,30,100,144,145,146,88,89,90],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":156,"publishedAt":34},"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",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000037","律师与法务",[157,134,136,158,159,160,161,141,162,142,76,163,100,164,165,166,89],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"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":177,"publishedAt":34},"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",[173,176],{"categoryNo":174,"categoryName":175,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":154,"categoryName":155,"taxonomyType":130,"taxonomyTypeDesc":131},[102,178,134,136,179,180,139,83,181,142,182,183,30,184,185,186,90,187,188,189],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":34},"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",[],[139,197,198,105,199,200,201,202,76,30,203,87,89,90],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]