[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DS6S4MW2KP6JHCZRQGT61V":3,"skill-same:01M6DS6S4MW2KP6JHCZRQGT61V":96},{"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":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M6DS6S4MW2KP6JHCZRQGT61V","monorepo-navigator",null,"Monorepo Navigator","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\u002Fmonorepo-navigator\u002FSKILL.md",[],[19,20,21],"navigator","monorepo","monorepo navigator","2026-11-10 10:12:30",false,"---\nname: \"monorepo-navigator\"\ndescription: \"Monorepo Navigator\"\n---\n\n# Monorepo Navigator\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Monorepo Architecture \u002F Build Systems  \n\n---\n\n## Overview\n\nNavigate, manage, and optimize monorepos. Covers Turborepo, Nx, pnpm workspaces, and Lerna. Enables cross-package impact analysis, selective builds\u002Ftests on affected packages only, remote caching, dependency graph visualization, and structured migrations from multi-repo to monorepo. Includes Claude Code configuration for workspace-aware development.\n\n---\n\n## Core Capabilities\n\n- **Cross-package impact analysis** — determine which apps break when a shared package changes\n- **Selective commands** — run tests\u002Fbuilds only for affected packages (not everything)\n- **Dependency graph** — visualize package relationships as Mermaid diagrams\n- **Build optimization** — remote caching, incremental builds, parallel execution\n- **Migration** — step-by-step multi-repo → monorepo with zero history loss\n- **Publishing** — changesets for versioning, pre-release channels, npm publish workflows\n- **Claude Code config** — workspace-aware CLAUDE.md with per-package instructions\n\n---\n\n## When to Use\n\nUse when:\n- Multiple packages\u002Fapps share code (UI components, utils, types, API clients)\n- Build times are slow because everything rebuilds when anything changes\n- Migrating from multiple repos to a single repo\n- Need to publish packages to npm with coordinated versioning\n- Teams work across multiple packages and need unified tooling\n\nSkip when:\n- Single-app project with no shared packages\n- Team\u002Fproject boundaries are completely isolated (polyrepo is fine)\n- Shared code is minimal and copy-paste overhead is acceptable\n\n---\n\n## Tool Selection\n\n| Tool | Best For | Key Feature |\n|---|---|---|\n| **Turborepo** | JS\u002FTS monorepos, simple pipeline config | Best-in-class remote caching, minimal config |\n| **Nx** | Large enterprises, plugin ecosystem | Project graph, code generation, affected commands |\n| **pnpm workspaces** | Workspace protocol, disk efficiency | `workspace:*` for local package refs |\n| **Lerna** | npm publishing, versioning | Batch publishing, conventional commits |\n| **Changesets** | Modern versioning (preferred over Lerna) | Changelog generation, pre-release channels |\n\nMost modern setups: **pnpm workspaces + Turborepo + Changesets**\n\n---\n\n## Turborepo\n→ See references\u002Fmonorepo-tooling-reference.md for details\n\n## Workspace Analyzer\n\n```bash\npython3 scripts\u002Fmonorepo_analyzer.py \u002Fpath\u002Fto\u002Fmonorepo\npython3 scripts\u002Fmonorepo_analyzer.py \u002Fpath\u002Fto\u002Fmonorepo --json\n```\n\nAlso see `references\u002Fmonorepo-patterns.md` for common architecture and CI patterns.\n\n## Common Pitfalls\n\n| Pitfall | Fix |\n|---|---|\n| Running `turbo run build` without `--filter` on every PR | Always use `--filter=...[origin\u002Fmain]` in CI |\n| `workspace:*` refs cause publish failures | Use `pnpm changeset publish` — it replaces `workspace:*` with real versions automatically |\n| All packages rebuild when unrelated file changes | Tune `inputs` in turbo.json to exclude docs, config files from cache keys |\n| Shared tsconfig causes one package to break all type-checks | Use `extends` properly — each package extends root but overrides `rootDir` \u002F `outDir` |\n| git history lost during migration | Use `git filter-repo --to-subdirectory-filter` before merging — never move files manually |\n| Remote cache not working in CI | Check TURBO_TOKEN and TURBO_TEAM env vars; verify with `turbo run build --summarize` |\n| CLAUDE.md too generic — Claude modifies wrong package | Add explicit \"When working on X, only touch files in apps\u002FX\" rules per package CLAUDE.md |\n\n---\n\n## Best Practices\n\n1. **Root CLAUDE.md defines the map** — document every package, its purpose, and dependency rules\n2. **Per-package CLAUDE.md defines the rules** — what's allowed, what's forbidden, testing commands\n3. **Always scope commands with --filter** — running everything on every change defeats the purpose\n4. **Remote cache is not optional** — without it, monorepo CI is slower than multi-repo CI\n5. **Changesets over manual versioning** — never hand-edit package.json versions in a monorepo\n6. **Shared configs in root, extended in packages** — tsconfig.base.json, .eslintrc.base.js, jest.base.config.js\n7. **Impact analysis before merging shared package changes** — run affected check, communicate blast radius\n8. **Keep packages\u002Ftypes as pure TypeScript** — no runtime code, no dependencies, fast to build and type-check\n","# Monorepo Navigator\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Monorepo Architecture \u002F Build Systems  \n\n---\n\n## Overview\n\nNavigate, manage, and optimize monorepos. Covers Turborepo, Nx, pnpm workspaces, and Lerna. Enables cross-package impact analysis, selective builds\u002Ftests on affected packages only, remote caching, dependency graph visualization, and structured migrations from multi-repo to monorepo. Includes Claude Code configuration for workspace-aware development.\n\n---\n\n## Core Capabilities\n\n- **Cross-package impact analysis** — determine which apps break when a shared package changes\n- **Selective commands** — run tests\u002Fbuilds only for affected packages (not everything)\n- **Dependency graph** — visualize package relationships as Mermaid diagrams\n- **Build optimization** — remote caching, incremental builds, parallel execution\n- **Migration** — step-by-step multi-repo → monorepo with zero history loss\n- **Publishing** — changesets for versioning, pre-release channels, npm publish workflows\n- **Claude Code config** — workspace-aware CLAUDE.md with per-package instructions\n\n---\n\n## When to Use\n\nUse when:\n- Multiple packages\u002Fapps share code (UI components, utils, types, API clients)\n- Build times are slow because everything rebuilds when anything changes\n- Migrating from multiple repos to a single repo\n- Need to publish packages to npm with coordinated versioning\n- Teams work across multiple packages and need unified tooling\n\nSkip when:\n- Single-app project with no shared packages\n- Team\u002Fproject boundaries are completely isolated (polyrepo is fine)\n- Shared code is minimal and copy-paste overhead is acceptable\n\n---\n\n## Tool Selection\n\n| Tool | Best For | Key Feature |\n|---|---|---|\n| **Turborepo** | JS\u002FTS monorepos, simple pipeline config | Best-in-class remote caching, minimal config |\n| **Nx** | Large enterprises, plugin ecosystem | Project graph, code generation, affected commands |\n| **pnpm workspaces** | Workspace protocol, disk efficiency | `workspace:*` for local package refs |\n| **Lerna** | npm publishing, versioning | Batch publishing, conventional commits |\n| **Changesets** | Modern versioning (preferred over Lerna) | Changelog generation, pre-release channels |\n\nMost modern setups: **pnpm workspaces + Turborepo + Changesets**\n\n---\n\n## Turborepo\n→ See references\u002Fmonorepo-tooling-reference.md for details\n\n## Workspace Analyzer\n\n```bash\npython3 scripts\u002Fmonorepo_analyzer.py \u002Fpath\u002Fto\u002Fmonorepo\npython3 scripts\u002Fmonorepo_analyzer.py \u002Fpath\u002Fto\u002Fmonorepo --json\n```\n\nAlso see `references\u002Fmonorepo-patterns.md` for common architecture and CI patterns.\n\n## Common Pitfalls\n\n| Pitfall | Fix |\n|---|---|\n| Running `turbo run build` without `--filter` on every PR | Always use `--filter=...[origin\u002Fmain]` in CI |\n| `workspace:*` refs cause publish failures | Use `pnpm changeset publish` — it replaces `workspace:*` with real versions automatically |\n| All packages rebuild when unrelated file changes | Tune `inputs` in turbo.json to exclude docs, config files from cache keys |\n| Shared tsconfig causes one package to break all type-checks | Use `extends` properly — each package extends root but overrides `rootDir` \u002F `outDir` |\n| git history lost during migration | Use `git filter-repo --to-subdirectory-filter` before merging — never move files manually |\n| Remote cache not working in CI | Check TURBO_TOKEN and TURBO_TEAM env vars; verify with `turbo run build --summarize` |\n| CLAUDE.md too generic — Claude modifies wrong package | Add explicit \"When working on X, only touch files in apps\u002FX\" rules per package CLAUDE.md |\n\n---\n\n## Best Practices\n\n1. **Root CLAUDE.md defines the map** — document every package, its purpose, and dependency rules\n2. **Per-package CLAUDE.md defines the rules** — what's allowed, what's forbidden, testing commands\n3. **Always scope commands with --filter** — running everything on every change defeats the purpose\n4. **Remote cache is not optional** — without it, monorepo CI is slower than multi-repo CI\n5. **Changesets over manual versioning** — never hand-edit package.json versions in a monorepo\n6. **Shared configs in root, extended in packages** — tsconfig.base.json, .eslintrc.base.js, jest.base.config.js\n7. **Impact analysis before merging shared package changes** — run affected check, communicate blast radius\n8. **Keep packages\u002Ftypes as pure TypeScript** — no runtime code, no dependencies, fast to build and type-check\n",{"name":5,"description":7},"main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","engineering\u002Fmonorepo-navigator",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill monorepo-navigator",{"tool":40,"command":41},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill monorepo-navigator",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill monorepo-navigator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fmonorepo-navigator\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82,86,92],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"algorithms.md","REFERENCE","参考文档",97,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsearcher-builder-relay-architecture\u002Falgorithms.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"failure_modes.md",100,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsearcher-builder-relay-architecture\u002Ffailure_modes.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"formulas.md",95,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsearcher-builder-relay-architecture\u002Fformulas.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"implementation_notes.md",107,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsearcher-builder-relay-architecture\u002Fimplementation_notes.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"integration_arbitragex.md",109,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsearcher-builder-relay-architecture\u002Fintegration_arbitragex.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"manifest.json",872,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsearcher-builder-relay-architecture\u002Fmanifest.json",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references.json",287,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsearcher-builder-relay-architecture\u002Freferences.json",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fmonorepo-patterns.md",1011,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fmonorepo-navigator\u002Freferences\u002Fmonorepo-patterns.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fmonorepo-tooling-reference.md",11999,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fmonorepo-navigator\u002Freferences\u002Fmonorepo-tooling-reference.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fmonorepo_analyzer.py","SCRIPT","脚本",5561,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering\u002Fmonorepo-navigator\u002Fscripts\u002Fmonorepo_analyzer.py",{"path":93,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":94,"sourceHtmlUrl":95},"validation_tests.md",103,"https:\u002F\u002Fgithub.com\u002Fhefarica\u002Farbitragex-v2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsearcher-builder-relay-architecture\u002Fvalidation_tests.md",[97,124,150,181,201,224],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":22},"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",[],[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","analysis","user","use","risk matrix","Market","device","control","iso","medical","iso 14971",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":22},"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",[],[131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,122,149],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","plan","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":166,"publishedAt":22},"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",[156,161],{"categoryNo":157,"categoryName":158,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":162,"categoryName":163,"taxonomyType":164,"taxonomyTypeDesc":165},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[167,168,169,170,171,172,134,173,174,175,176,177,116,132,178,179,180,120,121,122],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":190,"publishedAt":22},"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",[187],{"categoryNo":188,"categoryName":189,"taxonomyType":164,"taxonomyTypeDesc":165},"01JBSEEDCAT000000000000037","律师与法务",[191,168,170,192,193,194,195,175,196,176,106,197,132,198,199,200,121],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":211,"publishedAt":22},"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",[207,210],{"categoryNo":208,"categoryName":209,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":188,"categoryName":189,"taxonomyType":164,"taxonomyTypeDesc":165},[134,212,168,170,213,214,173,113,215,176,216,217,116,218,219,220,122,221,222,223],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":228,"categories":229,"keywords":230,"publishedAt":22},"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",[],[173,231,232,137,233,234,235,236,106,116,237,119,121,122],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]