[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DS28NCZCMM9712TGVCBXBQ":3,"skill-same:01M6DS28NCZCMM9712TGVCBXBQ":59},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M6DS28NCZCMM9712TGVCBXBQ","review",null,"Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics.","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\u002Fself-improving-agent\u002Fskills\u002Freview\u002FSKILL.md",[],[5,19,20,21,22,23,24,25],"memory","metrics","health","analyze","auto","stale","entries","2026-11-10 10:12:30",false,"---\nname: \"review\"\ndescription: \"Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics.\"\ncommand: \u002Fsi:review\n---\n\n# \u002Fsi:review — Analyze Auto-Memory\n\nPerforms a comprehensive audit of Claude Code's auto-memory and produces actionable recommendations.\n\n## Usage\n\n```\n\u002Fsi:review                    # Full review\n\u002Fsi:review --quick            # Summary only (counts + top 3 candidates)\n\u002Fsi:review --stale            # Focus on stale\u002Foutdated entries\n\u002Fsi:review --candidates       # Show only promotion candidates\n```\n\n## What It Does\n\n### Step 1: Locate memory directory\n\n```bash\n# Find the project's auto-memory directory\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\n\n# Fallback: check common path patterns\n# ~\u002F.claude\u002Fprojects\u002F\u003Cuser>\u002F\u003Cproject>\u002Fmemory\u002F\n# ~\u002F.claude\u002Fprojects\u002F\u003Cabsolute-path>\u002Fmemory\u002F\n\n# List all memory files\nls -la \"$MEMORY_DIR\"\u002F\n```\n\nIf memory directory doesn't exist, report that auto-memory may be disabled. Suggest checking with `\u002Fmemory`.\n\n### Step 2: Read and analyze MEMORY.md\n\nRead the full `MEMORY.md` file. Count lines and check against the 200-line startup limit.\n\nAnalyze each entry for:\n\n1. **Recurrence indicators**\n   - Same concept appears multiple times (different wording)\n   - References to \"again\" or \"still\" or \"keeps happening\"\n   - Similar entries across topic files\n\n2. **Staleness indicators**\n   - References files that no longer exist (`find` to verify)\n   - Mentions outdated tools, versions, or commands\n   - Contradicts current CLAUDE.md rules\n\n3. **Consolidation opportunities**\n   - Multiple entries about the same topic (e.g., three lines about testing)\n   - Entries that could merge into one concise rule\n\n4. **Promotion candidates** — entries that meet ALL criteria:\n   - Appeared in 2+ sessions (check wording patterns)\n   - Not project-specific trivia (broadly useful)\n   - Actionable (can be written as a concrete rule)\n   - Not already in CLAUDE.md or `.claude\u002Frules\u002F`\n\n### Step 3: Read topic files\n\nIf `MEMORY.md` references or the directory contains additional files (`debugging.md`, `patterns.md`, etc.):\n- Read each one\n- Cross-reference with MEMORY.md for duplicates\n- Check for entries that belong in the main file (high value) vs. topic files (details)\n\n### Step 4: Cross-reference with CLAUDE.md\n\nRead the project's `CLAUDE.md` (if it exists) and compare:\n- Are there MEMORY.md entries that duplicate CLAUDE.md rules? (→ remove from memory)\n- Are there MEMORY.md entries that contradict CLAUDE.md? (→ flag conflict)\n- Are there MEMORY.md patterns not yet in CLAUDE.md that should be? (→ promotion candidate)\n\nAlso check `.claude\u002Frules\u002F` directory for existing scoped rules.\n\n### Step 5: Generate report\n\nOutput format:\n\n```\n? Auto-Memory Review\n\nMemory Health:\n  MEMORY.md:        {{lines}}\u002F200 lines ({{percent}}%)\n  Topic files:      {{count}} ({{names}})\n  CLAUDE.md:        {{lines}} lines\n  Rules:            {{count}} files in .claude\u002Frules\u002F\n\n? Promotion Candidates ({{count}}):\n  1. \"{{pattern}}\" — seen {{n}}x, applies broadly\n     → Suggest: {{target}} (CLAUDE.md \u002F .claude\u002Frules\u002F{{name}}.md)\n  2. ...\n\n?️ Stale Entries ({{count}}):\n  1. Line {{n}}: \"{{entry}}\" — {{reason}}\n  2. ...\n\n? Consolidation ({{count}} groups):\n  1. Lines {{a}}, {{b}}, {{c}} all about {{topic}} → merge into 1 entry\n  2. ...\n\n⚠️ Conflicts ({{count}}):\n  1. MEMORY.md line {{n}} contradicts CLAUDE.md: {{detail}}\n\n? Recommendations:\n  - {{actionable suggestion}}\n  - {{actionable suggestion}}\n```\n\n## When to Use\n\n- After completing a major feature or debugging session\n- When `\u002Fsi:status` shows MEMORY.md is over 150 lines\n- Weekly during active development\n- Before starting a new project phase\n- After onboarding a new team member (review what Claude learned)\n\n## Tips\n\n- Run `\u002Fsi:review --quick` frequently (low overhead)\n- Full review is most valuable when MEMORY.md is getting crowded\n- Act on promotion candidates promptly — they're proven patterns\n- Don't hesitate to delete stale entries — auto-memory will re-learn if needed\n","# \u002Fsi:review — Analyze Auto-Memory\n\nPerforms a comprehensive audit of Claude Code's auto-memory and produces actionable recommendations.\n\n## Usage\n\n```\n\u002Fsi:review                    # Full review\n\u002Fsi:review --quick            # Summary only (counts + top 3 candidates)\n\u002Fsi:review --stale            # Focus on stale\u002Foutdated entries\n\u002Fsi:review --candidates       # Show only promotion candidates\n```\n\n## What It Does\n\n### Step 1: Locate memory directory\n\n```bash\n# Find the project's auto-memory directory\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\n\n# Fallback: check common path patterns\n# ~\u002F.claude\u002Fprojects\u002F\u003Cuser>\u002F\u003Cproject>\u002Fmemory\u002F\n# ~\u002F.claude\u002Fprojects\u002F\u003Cabsolute-path>\u002Fmemory\u002F\n\n# List all memory files\nls -la \"$MEMORY_DIR\"\u002F\n```\n\nIf memory directory doesn't exist, report that auto-memory may be disabled. Suggest checking with `\u002Fmemory`.\n\n### Step 2: Read and analyze MEMORY.md\n\nRead the full `MEMORY.md` file. Count lines and check against the 200-line startup limit.\n\nAnalyze each entry for:\n\n1. **Recurrence indicators**\n   - Same concept appears multiple times (different wording)\n   - References to \"again\" or \"still\" or \"keeps happening\"\n   - Similar entries across topic files\n\n2. **Staleness indicators**\n   - References files that no longer exist (`find` to verify)\n   - Mentions outdated tools, versions, or commands\n   - Contradicts current CLAUDE.md rules\n\n3. **Consolidation opportunities**\n   - Multiple entries about the same topic (e.g., three lines about testing)\n   - Entries that could merge into one concise rule\n\n4. **Promotion candidates** — entries that meet ALL criteria:\n   - Appeared in 2+ sessions (check wording patterns)\n   - Not project-specific trivia (broadly useful)\n   - Actionable (can be written as a concrete rule)\n   - Not already in CLAUDE.md or `.claude\u002Frules\u002F`\n\n### Step 3: Read topic files\n\nIf `MEMORY.md` references or the directory contains additional files (`debugging.md`, `patterns.md`, etc.):\n- Read each one\n- Cross-reference with MEMORY.md for duplicates\n- Check for entries that belong in the main file (high value) vs. topic files (details)\n\n### Step 4: Cross-reference with CLAUDE.md\n\nRead the project's `CLAUDE.md` (if it exists) and compare:\n- Are there MEMORY.md entries that duplicate CLAUDE.md rules? (→ remove from memory)\n- Are there MEMORY.md entries that contradict CLAUDE.md? (→ flag conflict)\n- Are there MEMORY.md patterns not yet in CLAUDE.md that should be? (→ promotion candidate)\n\nAlso check `.claude\u002Frules\u002F` directory for existing scoped rules.\n\n### Step 5: Generate report\n\nOutput format:\n\n```\n? Auto-Memory Review\n\nMemory Health:\n  MEMORY.md:        {{lines}}\u002F200 lines ({{percent}}%)\n  Topic files:      {{count}} ({{names}})\n  CLAUDE.md:        {{lines}} lines\n  Rules:            {{count}} files in .claude\u002Frules\u002F\n\n? Promotion Candidates ({{count}}):\n  1. \"{{pattern}}\" — seen {{n}}x, applies broadly\n     → Suggest: {{target}} (CLAUDE.md \u002F .claude\u002Frules\u002F{{name}}.md)\n  2. ...\n\n?️ Stale Entries ({{count}}):\n  1. Line {{n}}: \"{{entry}}\" — {{reason}}\n  2. ...\n\n? Consolidation ({{count}} groups):\n  1. Lines {{a}}, {{b}}, {{c}} all about {{topic}} → merge into 1 entry\n  2. ...\n\n⚠️ Conflicts ({{count}}):\n  1. MEMORY.md line {{n}} contradicts CLAUDE.md: {{detail}}\n\n? Recommendations:\n  - {{actionable suggestion}}\n  - {{actionable suggestion}}\n```\n\n## When to Use\n\n- After completing a major feature or debugging session\n- When `\u002Fsi:status` shows MEMORY.md is over 150 lines\n- Weekly during active development\n- Before starting a new project phase\n- After onboarding a new team member (review what Claude learned)\n\n## Tips\n\n- Run `\u002Fsi:review --quick` frequently (low overhead)\n- Full review is most valuable when MEMORY.md is getting crowded\n- Act on promotion candidates promptly — they're proven patterns\n- Don't hesitate to delete stale entries — auto-memory will re-learn if needed\n",{"name":5,"command":31,"description":7},"\u002Fsi:review","main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","engineering-team\u002Fself-improving-agent\u002Fskills\u002Freview",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":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill review",{"tool":45,"command":46},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill review",{"tool":48,"command":49},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fengineering-team\u002Fself-improving-agent\u002Fskills\u002Freview\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"package.json","REFERENCE","参考文档",204,"https:\u002F\u002Fgithub.com\u002Fxinyuehtx\u002Fskill-module\u002Fblob\u002Fmain\u002Fexamples\u002Fmulti-version\u002Fconsumer-b\u002Fpackage.json",[60,87,113,143,163,186],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":26},"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",[],[67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86],"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":26},"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",[],[94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,85,112],"regulatory affairs head","regulatory","head","documentation","documents","packages","planning","devices","plan","access","write","strategy","evidence","standards","manage","intelligence","across","strategies","clinical",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":129,"publishedAt":26},"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",[119,124],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[130,131,132,5,133,134,97,135,136,137,138,139,79,95,140,141,142,83,84,85],"quality manager qms iso13485","quality","design","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":26},"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",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000037","律师与法务",[153,131,5,154,155,156,157,137,158,138,69,159,95,160,161,162,84],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":173,"publishedAt":26},"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",[169,172],{"categoryNo":170,"categoryName":171,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":150,"categoryName":151,"taxonomyType":127,"taxonomyTypeDesc":128},[97,174,131,5,175,176,135,76,177,138,178,179,79,180,181,182,85,183,184,185],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":26},"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",[],[135,193,194,100,195,196,197,198,69,79,199,82,84,85],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]