[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QHZ7MZF0WM5PR8GST1MEXP":3,"skill-same:01M6QHZ7MZF0WM5PR8GST1MEXP":79},{"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":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":13,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6QHZ7MZF0WM5PR8GST1MEXP","frontend-staged-bundle-review",null,"Reviews staged git changes from a bundle size perspective. Analyzes change intent and provides optimization recommendations for React\u002FVue\u002FTaro\u002FNext.js projects. Should be used when the user is concerned about bundle size, code bloat, or package weight — before committing or evaluating new dependencies. Distinguished from frontend-code-review which focuses on code quality, this skill focuses specifically on bundle size impact analysis.","ImaginerLabs\u002Fskill-manager","ImaginerLabs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214277308?v=4","01M6QGGDPNF15RMMT1RCFDH9FN","01M6QGGDTH5BY64DQ123NR8M33",0,"MIT","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fcoding\u002Ffrontend-staged-bundle-review\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"review","frontend staged bundle review","staged","bundle","frontend","code","git","issues","code-review","analysis","projects","bundle size","intent","next","recommendations","change","impact","reviews","which","react","2026-11-10 10:12:30",false,"---\nname: frontend-staged-bundle-review\ndescription: >-\n  Reviews staged git changes from a bundle size perspective. Analyzes change intent and provides optimization\n  recommendations for React\u002FVue\u002FTaro\u002FNext.js projects. Should be used when the user is concerned about bundle\n  size, code bloat, or package weight — before committing or evaluating new dependencies.\n  Distinguished from frontend-code-review which focuses on code quality, this skill focuses specifically\n  on bundle size impact analysis.\ncategory: coding\nboundary:\n  vs_frontend-code-review: \"frontend-code-review focuses on general code quality issues, this skill focuses specifically on bundle size impact\"\n---\n\n# Frontend Staged Code Bundle Size Review\n\n## Core Capability\n\nBefore committing, read staged changes, analyze the change intent in project context, and review from a **bundle size** perspective — outputting high\u002Fmedium\u002Flow priority optimization recommendations.\n\n## When to Use\n\n- Worried about bundle size increase after feature iteration\n- Pre-evaluation before introducing new dependencies\n- Bundle size regression check after refactoring\n- Performance optimization audit\n- Mini-program main package size limit warning\n- First-screen load performance optimization\n- Taro mini-program, H5, React\u002FVue web, Next.js SSR projects\n\n## Skill Collaboration\n\n| Skill                    | How                                                                   | Use case                       |\n| ------------------------ | --------------------------------------------------------------------- | ------------------------------ |\n| **staged-code-review**   | Code quality review first, then bundle review                         | Comprehensive pre-commit check |\n| **frontend-code-review** | Use alongside, covering both quality and size                         | Combined code review           |\n| **tech-stack-detection** | Identify tech stack first, then targeted size analysis                | New project bundle review      |\n| **context-learning**     | Understand context when size issues involve complex dependency chains | Complex refactoring            |\n\n**Recommended workflow:**\n\n```\ngit add . → staged-code-review → frontend-staged-bundle-review → commit\n```\n\n---\n\n## Workflow\n\n### Step 1: Read Staged Diff\n\n```bash\ngit diff --staged\n```\n\n### Step 2: Analyze Change Intent\n\nUnderstand the business context of this change:\n\n- Read comments, variable names, function names in the diff to infer feature intent\n- Check for new `import` statements to identify introduced dependencies\n- Check existing project code (e.g., `package.json`, shared utilities) for duplicate imports\n- Identify the change type: new feature \u002F bug fix \u002F refactoring \u002F dependency upgrade\n\n### Step 3: Bundle Impact Analysis\n\nEvaluate impact across these dimensions:\n\n#### 3.1 Dependency Imports\n\n- Did new imports bring in large third-party libraries?\n- Is tree-shaking friendly (on-demand import) being used?\n- Can existing project utilities\u002Fcomponents replace the new import?\n- Are there duplicate-functionality libraries (e.g., both moment and dayjs)?\n\n#### 3.2 Code Redundancy\n\n- Duplicate logic that could be extracted into shared functions?\n- Large copy-pasted code blocks?\n- Dead code that's deprecated but not removed?\n- Debug code (console.log, debugger) not cleaned up?\n\n#### 3.3 Assets & Static Files\n\n- Inline Base64 images or large SVGs?\n- Hardcoded large JSON data that could be fetched dynamically?\n- Fonts\u002Ficons loaded on demand?\n- Images using appropriate formats (WebP\u002FAVIF) and compression?\n\n#### 3.4 Dynamic Loading Opportunities\n\n- New pages\u002Fmodules suitable for route-level lazy loading (`React.lazy` \u002F dynamic `import()`)?\n- Heavy components used infrequently that could be deferred?\n- Large third-party libraries that could be dynamically imported (e.g., ECharts, Monaco Editor)?\n- Next.js projects using `dynamic import` for first-screen optimization?\n\n#### 3.5 Taro\u002FMini-program Specifics\n\n- Web API polyfills that only work on H5?\n- Reasonable subpackage strategy, new pages in correct subpackages?\n- Heavy UI library full imports beyond `@tarojs\u002Fcomponents`?\n- Main package approaching the 2MB limit?\n\n#### 3.6 Next.js\u002FSSR Specifics\n\n- Using `next\u002Fdynamic` for component lazy loading?\n- Reasonably setting `ssr: false` for components that don't need SSR?\n- Using `next\u002Fimage` for image optimization?\n- Client-only libraries being bundled into the server bundle?\n\n### Step 4: Generate Prioritized Recommendations\n\n| Level         | Criteria                                                                  | Typical scenario                                                    |\n| ------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------- |\n| ? **High**   | Significant size impact (est. > 10KB gzip), or avoidable large dependency | Full lodash\u002Fmoment.js import; inline large images                   |\n| ? **Medium** | Moderate impact (est. 2–10KB gzip), or clear optimization path            | UI library not imported on-demand; new page not lazy-loaded         |\n| ? **Low**    | Small impact (est. \u003C 2KB gzip), best practice improvement                 | Small function replaceable by native; extractable duplicate utility |\n\n### Step 5: Output Optimization Report\n\n---\n\n## Output Format\n\n```markdown\n## ? Staged Code Bundle Size Review Report\n\n### Change Overview\n\n| Dimension     | Info                                                     |\n| ------------- | -------------------------------------------------------- |\n| File count    | X                                                        |\n| Tech stack    | [detected]                                               |\n| Change type   | New feature \u002F Bug fix \u002F Refactoring \u002F Dependency upgrade |\n| Change intent | [Inferred from diff]                                     |\n\n---\n\n### ? High Priority (significant size impact, fix before commit)\n\n| #   | File          | Issue   | Suggestion   | Est. savings | Scope                   |\n| --- | ------------- | ------- | ------------ | ------------ | ----------------------- |\n| 1   | `src\u002Fxxx.tsx` | [issue] | [suggestion] | ~XX KB       | First-screen\u002Fsubpackage |\n\n**Details:**\n\n- [Detailed analysis and optimization plan]\n\n---\n\n### ? Medium Priority (clear optimization path, fix this or next iteration)\n\n| #   | File          | Issue   | Suggestion   | Est. savings | Scope            |\n| --- | ------------- | ------- | ------------ | ------------ | ---------------- |\n| 1   | `src\u002Fxxx.tsx` | [issue] | [suggestion] | ~XX KB       | Non-first-screen |\n\n**Details:**\n\n- [Detailed analysis and optimization plan]\n\n---\n\n### ? Low Priority (best practice, fix as needed)\n\n| #   | File          | Issue   | Suggestion   | Est. savings |\n| --- | ------------- | ------- | ------------ | ------------ |\n| 1   | `src\u002Fxxx.tsx` | [issue] | [suggestion] | ~XX KB       |\n\n---\n\n### ? Size Impact Estimate\n\n| Category        | Current   | After optimization | Savings   |\n| --------------- | --------- | ------------------ | --------- |\n| High priority   | XX KB     | XX KB              | XX KB     |\n| Medium priority | XX KB     | XX KB              | XX KB     |\n| Low priority    | XX KB     | XX KB              | XX KB     |\n| **Total**       | **XX KB** | **XX KB**          | **XX KB** |\n\n---\n\n### ? Summary\n\n- High priority: X items (fix before commit)\n- Medium priority: X items (fix in next iteration)\n- Low priority: X items (best practice improvements)\n- **Overall assessment**: ? Size-friendly \u002F ? Room for optimization \u002F ? Fix before committing\n\n---\n\n### ? Next Steps\n\n- [ ] Fix high priority issues immediately\n- [ ] Address medium priority in next iteration\n- [ ] Monitor bundle size changes ongoing\n- [ ] Consider configuring bundle size monitoring (e.g., bundlesize, webpack-bundle-analyzer)\n```\n","# Frontend Staged Code Bundle Size Review\n\n## Core Capability\n\nBefore committing, read staged changes, analyze the change intent in project context, and review from a **bundle size** perspective — outputting high\u002Fmedium\u002Flow priority optimization recommendations.\n\n## When to Use\n\n- Worried about bundle size increase after feature iteration\n- Pre-evaluation before introducing new dependencies\n- Bundle size regression check after refactoring\n- Performance optimization audit\n- Mini-program main package size limit warning\n- First-screen load performance optimization\n- Taro mini-program, H5, React\u002FVue web, Next.js SSR projects\n\n## Skill Collaboration\n\n| Skill                    | How                                                                   | Use case                       |\n| ------------------------ | --------------------------------------------------------------------- | ------------------------------ |\n| **staged-code-review**   | Code quality review first, then bundle review                         | Comprehensive pre-commit check |\n| **frontend-code-review** | Use alongside, covering both quality and size                         | Combined code review           |\n| **tech-stack-detection** | Identify tech stack first, then targeted size analysis                | New project bundle review      |\n| **context-learning**     | Understand context when size issues involve complex dependency chains | Complex refactoring            |\n\n**Recommended workflow:**\n\n```\ngit add . → staged-code-review → frontend-staged-bundle-review → commit\n```\n\n---\n\n## Workflow\n\n### Step 1: Read Staged Diff\n\n```bash\ngit diff --staged\n```\n\n### Step 2: Analyze Change Intent\n\nUnderstand the business context of this change:\n\n- Read comments, variable names, function names in the diff to infer feature intent\n- Check for new `import` statements to identify introduced dependencies\n- Check existing project code (e.g., `package.json`, shared utilities) for duplicate imports\n- Identify the change type: new feature \u002F bug fix \u002F refactoring \u002F dependency upgrade\n\n### Step 3: Bundle Impact Analysis\n\nEvaluate impact across these dimensions:\n\n#### 3.1 Dependency Imports\n\n- Did new imports bring in large third-party libraries?\n- Is tree-shaking friendly (on-demand import) being used?\n- Can existing project utilities\u002Fcomponents replace the new import?\n- Are there duplicate-functionality libraries (e.g., both moment and dayjs)?\n\n#### 3.2 Code Redundancy\n\n- Duplicate logic that could be extracted into shared functions?\n- Large copy-pasted code blocks?\n- Dead code that's deprecated but not removed?\n- Debug code (console.log, debugger) not cleaned up?\n\n#### 3.3 Assets & Static Files\n\n- Inline Base64 images or large SVGs?\n- Hardcoded large JSON data that could be fetched dynamically?\n- Fonts\u002Ficons loaded on demand?\n- Images using appropriate formats (WebP\u002FAVIF) and compression?\n\n#### 3.4 Dynamic Loading Opportunities\n\n- New pages\u002Fmodules suitable for route-level lazy loading (`React.lazy` \u002F dynamic `import()`)?\n- Heavy components used infrequently that could be deferred?\n- Large third-party libraries that could be dynamically imported (e.g., ECharts, Monaco Editor)?\n- Next.js projects using `dynamic import` for first-screen optimization?\n\n#### 3.5 Taro\u002FMini-program Specifics\n\n- Web API polyfills that only work on H5?\n- Reasonable subpackage strategy, new pages in correct subpackages?\n- Heavy UI library full imports beyond `@tarojs\u002Fcomponents`?\n- Main package approaching the 2MB limit?\n\n#### 3.6 Next.js\u002FSSR Specifics\n\n- Using `next\u002Fdynamic` for component lazy loading?\n- Reasonably setting `ssr: false` for components that don't need SSR?\n- Using `next\u002Fimage` for image optimization?\n- Client-only libraries being bundled into the server bundle?\n\n### Step 4: Generate Prioritized Recommendations\n\n| Level         | Criteria                                                                  | Typical scenario                                                    |\n| ------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------- |\n| ? **High**   | Significant size impact (est. > 10KB gzip), or avoidable large dependency | Full lodash\u002Fmoment.js import; inline large images                   |\n| ? **Medium** | Moderate impact (est. 2–10KB gzip), or clear optimization path            | UI library not imported on-demand; new page not lazy-loaded         |\n| ? **Low**    | Small impact (est. \u003C 2KB gzip), best practice improvement                 | Small function replaceable by native; extractable duplicate utility |\n\n### Step 5: Output Optimization Report\n\n---\n\n## Output Format\n\n```markdown\n## ? Staged Code Bundle Size Review Report\n\n### Change Overview\n\n| Dimension     | Info                                                     |\n| ------------- | -------------------------------------------------------- |\n| File count    | X                                                        |\n| Tech stack    | [detected]                                               |\n| Change type   | New feature \u002F Bug fix \u002F Refactoring \u002F Dependency upgrade |\n| Change intent | [Inferred from diff]                                     |\n\n---\n\n### ? High Priority (significant size impact, fix before commit)\n\n| #   | File          | Issue   | Suggestion   | Est. savings | Scope                   |\n| --- | ------------- | ------- | ------------ | ------------ | ----------------------- |\n| 1   | `src\u002Fxxx.tsx` | [issue] | [suggestion] | ~XX KB       | First-screen\u002Fsubpackage |\n\n**Details:**\n\n- [Detailed analysis and optimization plan]\n\n---\n\n### ? Medium Priority (clear optimization path, fix this or next iteration)\n\n| #   | File          | Issue   | Suggestion   | Est. savings | Scope            |\n| --- | ------------- | ------- | ------------ | ------------ | ---------------- |\n| 1   | `src\u002Fxxx.tsx` | [issue] | [suggestion] | ~XX KB       | Non-first-screen |\n\n**Details:**\n\n- [Detailed analysis and optimization plan]\n\n---\n\n### ? Low Priority (best practice, fix as needed)\n\n| #   | File          | Issue   | Suggestion   | Est. savings |\n| --- | ------------- | ------- | ------------ | ------------ |\n| 1   | `src\u002Fxxx.tsx` | [issue] | [suggestion] | ~XX KB       |\n\n---\n\n### ? Size Impact Estimate\n\n| Category        | Current   | After optimization | Savings   |\n| --------------- | --------- | ------------------ | --------- |\n| High priority   | XX KB     | XX KB              | XX KB     |\n| Medium priority | XX KB     | XX KB              | XX KB     |\n| Low priority    | XX KB     | XX KB              | XX KB     |\n| **Total**       | **XX KB** | **XX KB**          | **XX KB** |\n\n---\n\n### ? Summary\n\n- High priority: X items (fix before commit)\n- Medium priority: X items (fix in next iteration)\n- Low priority: X items (best practice improvements)\n- **Overall assessment**: ? Size-friendly \u002F ? Room for optimization \u002F ? Fix before committing\n\n---\n\n### ? Next Steps\n\n- [ ] Fix high priority issues immediately\n- [ ] Address medium priority in next iteration\n- [ ] Monitor bundle size changes ongoing\n- [ ] Consider configuring bundle size monitoring (e.g., bundlesize, webpack-bundle-analyzer)\n```\n",{"name":5,"boundary":56,"category":58,"description":7},{"vs_frontend-code-review":57},"frontend-code-review focuses on general code quality issues, this skill focuses specifically on bundle size impact","coding","main","b9a52d8e27455bdad953d64928696d028223ea1b","skills\u002Fcoding\u002Ffrontend-staged-bundle-review","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager","https:\u002F\u002Fgithub.com\u002FImaginerLabs","2026-04-18 16:27:13",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add ImaginerLabs\u002Fskill-manager --skill frontend-staged-bundle-review",{"tool":71,"command":72},"bunx","bunx skills add ImaginerLabs\u002Fskill-manager --skill frontend-staged-bundle-review",{"tool":74,"command":75},"pnpm","pnpm dlx skills add ImaginerLabs\u002Fskill-manager --skill frontend-staged-bundle-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fcoding\u002Ffrontend-staged-bundle-review\u002FSKILL.md",true,[],[80,109,130,158,186,211],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":90,"publishedAt":51},"01M6QJCB2SD5KHC41ZDQC0GA1T","meeting-minutes","Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fmeeting-minutes\u002FSKILL.md",[86,87],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":88,"categoryName":89,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000034","行政与办公人员",[91,92,93,94,95,96,97,98,99,100,82,59,101,102,103,104,105,106,107,108],"meeting minutes","meeting","minutes","writing","github","copilot","generate","decisions","meetings","up","agenda","actionable","concise","follow-up","tree","true","action","for",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":51},"01M6QJC71RRGTGNNFEHJG6S20G","documentation-writer","Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdocumentation-writer\u002FSKILL.md",[],[116,117,118,94,95,96,119,120,121,122,123,124,59,125,126,127,128,105,106,129],"documentation","documentation writer","writer","https","quality","technical","technical writer","expert","documentation expert","structure","authoring","software","principles","high",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":143,"publishedAt":51},"01M6QJC0V3C7C4R9768J1AJYWY","doc-coauthoring","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdoc-coauthoring\u002FSKILL.md",[136,139,140],{"categoryNo":137,"categoryName":138,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":141,"categoryName":142,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000036","内容创作者",[144,145,94,146,147,116,148,149,150,151,152,153,59,154,155,126,156,157,105,108],"doc coauthoring","doc","workflow","official","tasks","decision","write","context","proposals","guide","refine","iteration","trigger","co",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":172,"publishedAt":51},"01M6QJBJ0YPVEWGEXZH3PJRRTT","code-review-workflow","Executes comprehensive 4-phase code review: basic review, quality check, bundle analysis, and test coverage. Should be used when the user mentions comprehensive code review, checking code quality, or reviewing staged changes with multi-phase analysis. This is the comprehensive review workflow, distinct from focused skills like frontend-code-review, staged-code-review, or code-change-test-designer.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-review-workflow\u002FSKILL.md",[164,167,170,171],{"categoryNo":165,"categoryName":166,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":168,"categoryName":169,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},[173,31,146,36,174,175,35,176,46,177,39,40,178,179,180,181,182,183,184,185],"code review","code review workflow","testing","test","code quality","check","coverage","quality check","basic","multi","comprehensive code review","with","phase",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":201,"publishedAt":51},"01M6QJB7XNHV3VEEQF4W7FMWF6","code-change-test-designer","Analyzes code changes and designs comprehensive test cases. Reads diffs, summarizes capability changes, and designs test cases covering main flows and edge cases. Should be used when the user mentions test coverage, designing tests for code changes, or analyzing diff\u002Fcommit for testing purposes. Distinguished from code-review-workflow which provides comprehensive review, this skill focuses on test case design for code changes.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-change-test-designer\u002FSKILL.md",[192,193,196,197,198],{"categoryNo":168,"categoryName":169,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":194,"categoryName":195,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},{"categoryNo":199,"categoryName":200,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师",[176,46,36,202,203,175,204,205,146,206,39,207,179,208,59,209,210,49,108,185],"designer","code change test designer","design","diffs","commit","edge","diff","tests","flows",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":218,"publishedAt":51},"01M6QJB195WD7DCJWDMKWKB29S","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmeta-skills\u002Fskill-creator\u002FSKILL.md",[217],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[219,220,221,222,147,223,224,225,226,227,40,228,229,230,59,231,232,105,108,213],"skill creator","creator","performance","run evals","variance analysis","create","run","benchmark","Meta","improve","edit","evals","optimize","existing skill"]