[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBCJWJ9ZF8B2AD4E34456Z":3,"skill-same:01M6KBCJWJ9ZF8B2AD4E34456Z":76},{"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":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M6KBCJWJ9ZF8B2AD4E34456Z","git-worktree-manager",null,"Git Worktree Manager","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fgit-worktree-manager\u002FSKILL.md",[],[19,20,21,22,23,24],"git","worktree manager","worktree","git worktree","git worktree manager","manager","2026-11-10 10:12:30",false,"---\nname: \"git-worktree-manager\"\ndescription: \"Git Worktree Manager\"\n---\n\n# Git Worktree Manager\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Parallel Development & Branch Isolation\n\n## Overview\n\nUse this skill to run parallel feature work safely with Git worktrees. It standardizes branch isolation, port allocation, environment sync, and cleanup so each worktree behaves like an independent local app without stepping on another branch.\n\nThis skill is optimized for multi-agent workflows where each agent or terminal session owns one worktree.\n\n## Core Capabilities\n\n- Create worktrees from new or existing branches with deterministic naming\n- Auto-allocate non-conflicting ports per worktree and persist assignments\n- Copy local environment files (`.env*`) from main repo to new worktree\n- Optionally install dependencies based on lockfile detection\n- Detect stale worktrees and uncommitted changes before cleanup\n- Identify merged branches and safely remove outdated worktrees\n\n## When to Use\n\n- You need 2+ concurrent branches open locally\n- You want isolated dev servers for feature, hotfix, and PR validation\n- You are working with multiple agents that must not share a branch\n- Your current branch is blocked but you need to ship a quick fix now\n- You want repeatable cleanup instead of ad-hoc `rm -rf` operations\n\n## Key Workflows\n\n### 1. Create a Fully-Prepared Worktree\n\n1. Pick a branch name and worktree name.\n2. Run the manager script (creates branch if missing).\n3. Review generated port map.\n4. Start app using allocated ports.\n\n```bash\npython scripts\u002Fworktree_manager.py \\\n  --repo . \\\n  --branch feature\u002Fnew-auth \\\n  --name wt-auth \\\n  --base-branch main \\\n  --install-deps \\\n  --format text\n```\n\nIf you use JSON automation input:\n\n```bash\ncat config.json | python scripts\u002Fworktree_manager.py --format json\n# or\npython scripts\u002Fworktree_manager.py --input config.json --format json\n```\n\n### 2. Run Parallel Sessions\n\nRecommended convention:\n\n- Main repo: integration branch (`main`\u002F`develop`) on default port\n- Worktree A: feature branch + offset ports\n- Worktree B: hotfix branch + next offset\n\nEach worktree contains `.worktree-ports.json` with assigned ports.\n\n### 3. Cleanup with Safety Checks\n\n1. Scan all worktrees and stale age.\n2. Inspect dirty trees and branch merge status.\n3. Remove only merged + clean worktrees, or force explicitly.\n\n```bash\npython scripts\u002Fworktree_cleanup.py --repo . --stale-days 14 --format text\npython scripts\u002Fworktree_cleanup.py --repo . --remove-merged --format text\n```\n\n### 4. Docker Compose Pattern\n\nUse per-worktree override files mapped from allocated ports. The script outputs a deterministic port map; apply it to `docker-compose.worktree.yml`.\n\nSee [docker-compose-patterns.md](references\u002Fdocker-compose-patterns.md) for concrete templates.\n\n### 5. Port Allocation Strategy\n\nDefault strategy is `base + (index * stride)` with collision checks:\n\n- App: `3000`\n- Postgres: `5432`\n- Redis: `6379`\n- Stride: `10`\n\nSee [port-allocation-strategy.md](references\u002Fport-allocation-strategy.md) for the full strategy and edge cases.\n\n## Script Interfaces\n\n- `python scripts\u002Fworktree_manager.py --help`\n  - Create\u002Flist worktrees\n  - Allocate\u002Fpersist ports\n  - Copy `.env*` files\n  - Optional dependency installation\n- `python scripts\u002Fworktree_cleanup.py --help`\n  - Stale detection by age\n  - Dirty-state detection\n  - Merged-branch detection\n  - Optional safe removal\n\nBoth tools support stdin JSON and `--input` file mode for automation pipelines.\n\n## Common Pitfalls\n\n1. Creating worktrees inside the main repo directory\n2. Reusing `localhost:3000` across all branches\n3. Sharing one database URL across isolated feature branches\n4. Removing a worktree with uncommitted changes\n5. Forgetting to prune old metadata after branch deletion\n6. Assuming merged status without checking against the target branch\n\n## Best Practices\n\n1. One branch per worktree, one agent per worktree.\n2. Keep worktrees short-lived; remove after merge.\n3. Use a deterministic naming pattern (`wt-\u003Ctopic>`).\n4. Persist port mappings in file, not memory or terminal notes.\n5. Run cleanup scan weekly in active repos.\n6. Use `--format json` for machine flows and `--format text` for human review.\n7. Never force-remove dirty worktrees unless changes are intentionally discarded.\n\n## Validation Checklist\n\nBefore claiming setup complete:\n\n1. `git worktree list` shows expected path + branch.\n2. `.worktree-ports.json` exists and contains unique ports.\n3. `.env` files copied successfully (if present in source repo).\n4. Dependency install command exits with code `0` (if enabled).\n5. Cleanup scan reports no unintended stale dirty trees.\n\n## References\n\n- [port-allocation-strategy.md](references\u002Fport-allocation-strategy.md)\n- [docker-compose-patterns.md](references\u002Fdocker-compose-patterns.md)\n- [README.md](README.md) for quick start and installation details\n\n## Decision Matrix\n\nUse this quick selector before creating a new worktree:\n\n- Need isolated dependencies and server ports -> create a new worktree\n- Need only a quick local diff review -> stay on current tree\n- Need hotfix while feature branch is dirty -> create dedicated hotfix worktree\n- Need ephemeral reproduction branch for bug triage -> create temporary worktree and cleanup same day\n\n## Operational Checklist\n\n### Before Creation\n\n1. Confirm main repo has clean baseline or intentional WIP commits.\n2. Confirm target branch naming convention.\n3. Confirm required base branch exists (`main`\u002F`develop`).\n4. Confirm no reserved local ports are already occupied by non-repo services.\n\n### After Creation\n\n1. Verify `git status` branch matches expected branch.\n2. Verify `.worktree-ports.json` exists.\n3. Verify app boots on allocated app port.\n4. Verify DB and cache endpoints target isolated ports.\n\n### Before Removal\n\n1. Verify branch has upstream and is merged when intended.\n2. Verify no uncommitted files remain.\n3. Verify no running containers\u002Fprocesses depend on this worktree path.\n\n## CI and Team Integration\n\n- Use worktree path naming that maps to task ID (`wt-1234-auth`).\n- Include the worktree path in terminal title to avoid wrong-window commits.\n- In automated setups, persist creation metadata in CI artifacts\u002Flogs.\n- Trigger cleanup report in scheduled jobs and post summary to team channel.\n\n## Failure Recovery\n\n- If `git worktree add` fails due to existing path: inspect path, do not overwrite.\n- If dependency install fails: keep worktree created, mark status and continue manual recovery.\n- If env copy fails: continue with warning and explicit missing file list.\n- If port allocation collides with external service: rerun with adjusted base ports.\n","# Git Worktree Manager\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Parallel Development & Branch Isolation\n\n## Overview\n\nUse this skill to run parallel feature work safely with Git worktrees. It standardizes branch isolation, port allocation, environment sync, and cleanup so each worktree behaves like an independent local app without stepping on another branch.\n\nThis skill is optimized for multi-agent workflows where each agent or terminal session owns one worktree.\n\n## Core Capabilities\n\n- Create worktrees from new or existing branches with deterministic naming\n- Auto-allocate non-conflicting ports per worktree and persist assignments\n- Copy local environment files (`.env*`) from main repo to new worktree\n- Optionally install dependencies based on lockfile detection\n- Detect stale worktrees and uncommitted changes before cleanup\n- Identify merged branches and safely remove outdated worktrees\n\n## When to Use\n\n- You need 2+ concurrent branches open locally\n- You want isolated dev servers for feature, hotfix, and PR validation\n- You are working with multiple agents that must not share a branch\n- Your current branch is blocked but you need to ship a quick fix now\n- You want repeatable cleanup instead of ad-hoc `rm -rf` operations\n\n## Key Workflows\n\n### 1. Create a Fully-Prepared Worktree\n\n1. Pick a branch name and worktree name.\n2. Run the manager script (creates branch if missing).\n3. Review generated port map.\n4. Start app using allocated ports.\n\n```bash\npython scripts\u002Fworktree_manager.py \\\n  --repo . \\\n  --branch feature\u002Fnew-auth \\\n  --name wt-auth \\\n  --base-branch main \\\n  --install-deps \\\n  --format text\n```\n\nIf you use JSON automation input:\n\n```bash\ncat config.json | python scripts\u002Fworktree_manager.py --format json\n# or\npython scripts\u002Fworktree_manager.py --input config.json --format json\n```\n\n### 2. Run Parallel Sessions\n\nRecommended convention:\n\n- Main repo: integration branch (`main`\u002F`develop`) on default port\n- Worktree A: feature branch + offset ports\n- Worktree B: hotfix branch + next offset\n\nEach worktree contains `.worktree-ports.json` with assigned ports.\n\n### 3. Cleanup with Safety Checks\n\n1. Scan all worktrees and stale age.\n2. Inspect dirty trees and branch merge status.\n3. Remove only merged + clean worktrees, or force explicitly.\n\n```bash\npython scripts\u002Fworktree_cleanup.py --repo . --stale-days 14 --format text\npython scripts\u002Fworktree_cleanup.py --repo . --remove-merged --format text\n```\n\n### 4. Docker Compose Pattern\n\nUse per-worktree override files mapped from allocated ports. The script outputs a deterministic port map; apply it to `docker-compose.worktree.yml`.\n\nSee [docker-compose-patterns.md](references\u002Fdocker-compose-patterns.md) for concrete templates.\n\n### 5. Port Allocation Strategy\n\nDefault strategy is `base + (index * stride)` with collision checks:\n\n- App: `3000`\n- Postgres: `5432`\n- Redis: `6379`\n- Stride: `10`\n\nSee [port-allocation-strategy.md](references\u002Fport-allocation-strategy.md) for the full strategy and edge cases.\n\n## Script Interfaces\n\n- `python scripts\u002Fworktree_manager.py --help`\n  - Create\u002Flist worktrees\n  - Allocate\u002Fpersist ports\n  - Copy `.env*` files\n  - Optional dependency installation\n- `python scripts\u002Fworktree_cleanup.py --help`\n  - Stale detection by age\n  - Dirty-state detection\n  - Merged-branch detection\n  - Optional safe removal\n\nBoth tools support stdin JSON and `--input` file mode for automation pipelines.\n\n## Common Pitfalls\n\n1. Creating worktrees inside the main repo directory\n2. Reusing `localhost:3000` across all branches\n3. Sharing one database URL across isolated feature branches\n4. Removing a worktree with uncommitted changes\n5. Forgetting to prune old metadata after branch deletion\n6. Assuming merged status without checking against the target branch\n\n## Best Practices\n\n1. One branch per worktree, one agent per worktree.\n2. Keep worktrees short-lived; remove after merge.\n3. Use a deterministic naming pattern (`wt-\u003Ctopic>`).\n4. Persist port mappings in file, not memory or terminal notes.\n5. Run cleanup scan weekly in active repos.\n6. Use `--format json` for machine flows and `--format text` for human review.\n7. Never force-remove dirty worktrees unless changes are intentionally discarded.\n\n## Validation Checklist\n\nBefore claiming setup complete:\n\n1. `git worktree list` shows expected path + branch.\n2. `.worktree-ports.json` exists and contains unique ports.\n3. `.env` files copied successfully (if present in source repo).\n4. Dependency install command exits with code `0` (if enabled).\n5. Cleanup scan reports no unintended stale dirty trees.\n\n## References\n\n- [port-allocation-strategy.md](references\u002Fport-allocation-strategy.md)\n- [docker-compose-patterns.md](references\u002Fdocker-compose-patterns.md)\n- [README.md](README.md) for quick start and installation details\n\n## Decision Matrix\n\nUse this quick selector before creating a new worktree:\n\n- Need isolated dependencies and server ports -> create a new worktree\n- Need only a quick local diff review -> stay on current tree\n- Need hotfix while feature branch is dirty -> create dedicated hotfix worktree\n- Need ephemeral reproduction branch for bug triage -> create temporary worktree and cleanup same day\n\n## Operational Checklist\n\n### Before Creation\n\n1. Confirm main repo has clean baseline or intentional WIP commits.\n2. Confirm target branch naming convention.\n3. Confirm required base branch exists (`main`\u002F`develop`).\n4. Confirm no reserved local ports are already occupied by non-repo services.\n\n### After Creation\n\n1. Verify `git status` branch matches expected branch.\n2. Verify `.worktree-ports.json` exists.\n3. Verify app boots on allocated app port.\n4. Verify DB and cache endpoints target isolated ports.\n\n### Before Removal\n\n1. Verify branch has upstream and is merged when intended.\n2. Verify no uncommitted files remain.\n3. Verify no running containers\u002Fprocesses depend on this worktree path.\n\n## CI and Team Integration\n\n- Use worktree path naming that maps to task ID (`wt-1234-auth`).\n- Include the worktree path in terminal title to avoid wrong-window commits.\n- In automated setups, persist creation metadata in CI artifacts\u002Flogs.\n- Trigger cleanup report in scheduled jobs and post summary to team channel.\n\n## Failure Recovery\n\n- If `git worktree add` fails due to existing path: inspect path, do not overwrite.\n- If dependency install fails: keep worktree created, mark status and continue manual recovery.\n- If env copy fails: continue with warning and explicit missing file list.\n- If port allocation collides with external service: rerun with adjusted base ports.\n",{"name":5,"description":7},"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering\u002Fgit-worktree-manager",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill git-worktree-manager",{"tool":44,"command":45},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill git-worktree-manager",{"tool":47,"command":48},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill git-worktree-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fgit-worktree-manager\u002FSKILL.md",true,[52,58,62,66,72],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"README.md","REFERENCE","参考文档",1291,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fgit-worktree-manager\u002FREADME.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fdocker-compose-patterns.md",1149,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fgit-worktree-manager\u002Freferences\u002Fdocker-compose-patterns.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fport-allocation-strategy.md",1030,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fgit-worktree-manager\u002Freferences\u002Fport-allocation-strategy.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fworktree_cleanup.py","SCRIPT","脚本",6620,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fgit-worktree-manager\u002Fscripts\u002Fworktree_cleanup.py",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Fworktree_manager.py",8566,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fgit-worktree-manager\u002Fscripts\u002Fworktree_manager.py",[77,109,134,158,190,210],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":88,"publishedAt":25},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":25},"01M6KC461R3GKGZ1TAYHVR1MW9","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\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[116,117,118,119,120,121,122,123,96,97,124,125,126,127,128,129,130,131,132,133],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":25},"01M6KC3HF5ZFSSP2NZF68PEPFB","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\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[141,142,143,144,145,146,147,148,149,97,150,151,152,153,154,155,156,157,24,108],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":172,"publishedAt":25},"01M6KC34Z8M1559EY1CXYBJB1A","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\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[164,169],{"categoryNo":165,"categoryName":166,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":170,"categoryName":171,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000032","设计师",[173,174,24,175,176,177,178,179,180,97,181,182,183,184,185,186,187,188,108,189],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"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":197,"publishedAt":25},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","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\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[196],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},[198,174,24,199,200,201,202,203,89,204,180,205,142,206,207,208,125,185,108,209],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":223,"publishedAt":25},"01M6KC1VRR5JTDBNZANHPS6VR6","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\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[216,219,222],{"categoryNo":217,"categoryName":218,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":220,"categoryName":221,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},[224,225,174,24,199,226,227,93,180,228,229,230,231,232,126,233,234,235,236,108],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]