[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QJ8AD1R44BEX9QRBS5B9CG":3,"skill-same:01M6QJ8AD1R44BEX9QRBS5B9CG":84},{"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":25,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":13,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6QJ8AD1R44BEX9QRBS5B9CG","feature-port-doc-generator",null,"Generates standardized porting documentation from completed feature changes. Analyzes commit diffs or file contents, extracts change intent, and outputs Markdown documentation for cross-team understanding. Should be used when the user needs to document a change for cross-team or cross-project consumption. Distinguished from cross-branch-fix-porter which actively re-implements fixes, this skill documents changes.","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\u002Fdev-tools\u002Ffeature-port-doc-generator\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"feature port doc generator","doc","generator","doc generator","port","feature","across","porting","which","re","project","diffs","branches","fix","branch","team","documents","documentation","commit","change","2026-11-10 10:12:30",false,"---\nname: feature-port-doc-generator\ndescription: >-\n  Generates standardized porting documentation from completed feature changes. Analyzes commit diffs or file contents,\n  extracts change intent, and outputs Markdown documentation for cross-team understanding.\n  Should be used when the user needs to document a change for cross-team or cross-project consumption.\n  Distinguished from cross-branch-fix-porter which actively re-implements fixes, this skill documents changes.\ncategory: dev-tools\nboundary:\n  vs_cross-branch-fix-porter: \"cross-branch-fix-porter actively re-implements fixes across branches, this skill documents changes for other teams\"\n---\n\n# Feature Porting Document Generator\n\n## Core Approach\n\nNot copying code — transmitting intent. Let the receiving team understand \"what changed, why it changed, and how to implement it in their own project.\"\n\n## When to Use\n\n- User provides a commit ID that needs to be documented as a porting guide\n- User provides one or more changed files and needs to extract the change intent\n- A feature implementation needs to be shared with other project teams\n\n## Workflow\n\n### Phase 1: Get Change Information\n\n**Case A: User provided a commit ID**\n\n```\n1. Get commit basic info (message, author, time)\n2. Get commit code diff\n3. Count changed files, assess change scope\n```\n\n**Case B: User specified file paths (no commit ID)**\n\n```\n1. Read the user-specified file contents\n2. Find recent related commit history for those files\n3. Confirm the relevant commits and get their diffs\n```\n\n### Phase 2: Analyze Change Intent\n\n```\n1. [Change type] What kind of change is this? (New feature \u002F Bug fix \u002F Performance optimization \u002F Refactoring)\n2. [Problem\u002FGoal] What problem does this change solve, or what goal does it achieve?\n3. [Change scope] Which files are involved? What's the purpose of each file's change?\n4. [Core logic] What's the key behavioral change (not code change)?\n5. [External dependencies] Does the change introduce new dependencies (npm packages, utility functions, components, APIs)?\n6. [Porting prerequisites] What baseline conditions must other projects meet before porting?\n```\n\n### Phase 3: Collect File Paths\n\n```\n1. For file paths in the commit diff, combine with project root to form absolute paths\n2. Use git rev-parse --show-toplevel to get the project root\n3. All file paths in the final document should use absolute path format\n```\n\n### Phase 4: Assess Porting Complexity\n\n| Complexity  | Criteria                                                                      | Porting advice                             |\n| ----------- | ----------------------------------------------------------------------------- | ------------------------------------------ |\n| **Simple**  | Single file change, no new dependencies, independent logic                    | Can directly reference code implementation |\n| **Medium**  | Multi-file change, few dependencies, related logic                            | Port file by file in order                 |\n| **Complex** | Involves architectural changes, many dependencies, requires prerequisite work | Port in phases                             |\n\n### Phase 5: Generate Porting Document\n\nThe document must include these sections:\n\n- Change overview (type, goal, background)\n- File scope (file list + change description)\n- Core logic explanation (before\u002Fafter behavior comparison)\n- Dependency list (new dependencies, prerequisites)\n- Porting steps (step-by-step instructions)\n- Notes (common issues, risk points)\n\n---\n\n## Output Format\n\n```markdown\n## [Feature Name] Porting Document\n\n### Change Overview\n\n- **Type**: New feature \u002F Bug fix \u002F Performance optimization \u002F Refactoring\n- **Goal**: [One-sentence description]\n- **Background**: [Why this change was needed]\n\n### File Scope\n\n| File path           | Change description  |\n| ------------------- | ------------------- |\n| \u002Fabs\u002Fpath\u002Ffile1.ts  | [Purpose of change] |\n| \u002Fabs\u002Fpath\u002Ffile2.tsx | [Purpose of change] |\n\n### Core Logic Explanation\n\n**Before**: [Original behavior]\n\n**After**: [New behavior]\n\n### Dependency List\n\n**New dependencies**:\n\n- [Dependency package\u002Futility function\u002Fcomponent]\n\n**Prerequisites**:\n\n- [Baseline conditions the project must meet]\n\n### Porting Steps\n\n1. [Step 1: specific action]\n2. [Step 2: specific action]\n3. [Step 3: specific action]\n\n### Notes\n\n- [Risk point or common issue]\n```\n\n---\n\n## Important Notes\n\n- **Paths must be absolute** — All file paths in the document must use absolute paths\n- **Intent over code** — The core of the document is communicating \"why it changed\"\n- **Reader's perspective** — Write for someone who doesn't know the original project\n- **Dependencies must be complete** — All newly introduced dependencies must be listed\n- **Steps must be executable** — Porting steps must be specific enough to follow\n","# Feature Porting Document Generator\n\n## Core Approach\n\nNot copying code — transmitting intent. Let the receiving team understand \"what changed, why it changed, and how to implement it in their own project.\"\n\n## When to Use\n\n- User provides a commit ID that needs to be documented as a porting guide\n- User provides one or more changed files and needs to extract the change intent\n- A feature implementation needs to be shared with other project teams\n\n## Workflow\n\n### Phase 1: Get Change Information\n\n**Case A: User provided a commit ID**\n\n```\n1. Get commit basic info (message, author, time)\n2. Get commit code diff\n3. Count changed files, assess change scope\n```\n\n**Case B: User specified file paths (no commit ID)**\n\n```\n1. Read the user-specified file contents\n2. Find recent related commit history for those files\n3. Confirm the relevant commits and get their diffs\n```\n\n### Phase 2: Analyze Change Intent\n\n```\n1. [Change type] What kind of change is this? (New feature \u002F Bug fix \u002F Performance optimization \u002F Refactoring)\n2. [Problem\u002FGoal] What problem does this change solve, or what goal does it achieve?\n3. [Change scope] Which files are involved? What's the purpose of each file's change?\n4. [Core logic] What's the key behavioral change (not code change)?\n5. [External dependencies] Does the change introduce new dependencies (npm packages, utility functions, components, APIs)?\n6. [Porting prerequisites] What baseline conditions must other projects meet before porting?\n```\n\n### Phase 3: Collect File Paths\n\n```\n1. For file paths in the commit diff, combine with project root to form absolute paths\n2. Use git rev-parse --show-toplevel to get the project root\n3. All file paths in the final document should use absolute path format\n```\n\n### Phase 4: Assess Porting Complexity\n\n| Complexity  | Criteria                                                                      | Porting advice                             |\n| ----------- | ----------------------------------------------------------------------------- | ------------------------------------------ |\n| **Simple**  | Single file change, no new dependencies, independent logic                    | Can directly reference code implementation |\n| **Medium**  | Multi-file change, few dependencies, related logic                            | Port file by file in order                 |\n| **Complex** | Involves architectural changes, many dependencies, requires prerequisite work | Port in phases                             |\n\n### Phase 5: Generate Porting Document\n\nThe document must include these sections:\n\n- Change overview (type, goal, background)\n- File scope (file list + change description)\n- Core logic explanation (before\u002Fafter behavior comparison)\n- Dependency list (new dependencies, prerequisites)\n- Porting steps (step-by-step instructions)\n- Notes (common issues, risk points)\n\n---\n\n## Output Format\n\n```markdown\n## [Feature Name] Porting Document\n\n### Change Overview\n\n- **Type**: New feature \u002F Bug fix \u002F Performance optimization \u002F Refactoring\n- **Goal**: [One-sentence description]\n- **Background**: [Why this change was needed]\n\n### File Scope\n\n| File path           | Change description  |\n| ------------------- | ------------------- |\n| \u002Fabs\u002Fpath\u002Ffile1.ts  | [Purpose of change] |\n| \u002Fabs\u002Fpath\u002Ffile2.tsx | [Purpose of change] |\n\n### Core Logic Explanation\n\n**Before**: [Original behavior]\n\n**After**: [New behavior]\n\n### Dependency List\n\n**New dependencies**:\n\n- [Dependency package\u002Futility function\u002Fcomponent]\n\n**Prerequisites**:\n\n- [Baseline conditions the project must meet]\n\n### Porting Steps\n\n1. [Step 1: specific action]\n2. [Step 2: specific action]\n3. [Step 3: specific action]\n\n### Notes\n\n- [Risk point or common issue]\n```\n\n---\n\n## Important Notes\n\n- **Paths must be absolute** — All file paths in the document must use absolute paths\n- **Intent over code** — The core of the document is communicating \"why it changed\"\n- **Reader's perspective** — Write for someone who doesn't know the original project\n- **Dependencies must be complete** — All newly introduced dependencies must be listed\n- **Steps must be executable** — Porting steps must be specific enough to follow\n",{"name":5,"boundary":51,"category":53,"description":7},{"vs_cross-branch-fix-porter":52},"cross-branch-fix-porter actively re-implements fixes across branches, this skill documents changes for other teams","dev-tools","main","b9a52d8e27455bdad953d64928696d028223ea1b","skills\u002Fdev-tools\u002Ffeature-port-doc-generator","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager","https:\u002F\u002Fgithub.com\u002FImaginerLabs","2026-04-18 16:27:13",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add ImaginerLabs\u002Fskill-manager --skill feature-port-doc-generator",{"tool":66,"command":67},"bunx","bunx skills add ImaginerLabs\u002Fskill-manager --skill feature-port-doc-generator",{"tool":69,"command":70},"pnpm","pnpm dlx skills add ImaginerLabs\u002Fskill-manager --skill feature-port-doc-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Ffeature-port-doc-generator\u002FSKILL.md",true,[74,80],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fport-doc-template.md","REFERENCE","参考文档",10154,"https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Ffeature-port-doc-generator\u002Freferences\u002Fport-doc-template.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fworkflow.md",8030,"https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Ffeature-port-doc-generator\u002Freferences\u002Fworkflow.md",[85,116,136,163,198,221],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":97,"publishedAt":46},"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",[91,92],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[98,99,100,101,102,103,104,105,106,107,87,54,108,109,110,111,112,113,114,115],"meeting minutes","meeting","minutes","writing","github","copilot","generate","decisions","meetings","up","agenda","actionable","concise","follow-up","tree","true","action","for",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":46},"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",[],[43,123,124,101,102,103,125,126,127,128,129,130,54,131,132,133,134,112,113,135],"documentation writer","writer","https","quality","technical","technical writer","expert","documentation expert","structure","authoring","software","principles","high",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":149,"publishedAt":46},"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",[142,145,146],{"categoryNo":143,"categoryName":144,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":147,"categoryName":148,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000036","内容创作者",[150,27,101,151,152,43,153,154,155,156,157,158,54,159,160,132,161,162,112,115],"doc coauthoring","workflow","official","tasks","decision","write","context","proposals","guide","refine","iteration","trigger","co",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":179,"publishedAt":46},"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",[169,172,175,176],{"categoryNo":170,"categoryName":171,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":173,"categoryName":174,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":177,"categoryName":178,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000030","开发工程师",[180,181,151,182,183,184,185,186,45,187,188,189,190,191,192,193,194,195,196,197],"code review","review","code","code review workflow","testing","frontend","test","code quality","code-review","analysis","check","coverage","quality check","basic","multi","comprehensive code review","with","phase",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":213,"publishedAt":46},"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",[204,205,208,209,210],{"categoryNo":173,"categoryName":174,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":206,"categoryName":207,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":177,"categoryName":178,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":211,"categoryName":212,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000032","设计师",[186,45,182,214,215,184,216,37,151,44,188,217,191,218,54,219,220,34,115,197],"designer","code change test designer","design","edge","diff","tests","flows",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":228,"publishedAt":46},"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",[227],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[229,230,231,232,152,233,234,235,236,237,189,238,239,240,54,241,242,112,115,223],"skill creator","creator","performance","run evals","variance analysis","create","run","benchmark","Meta","improve","edit","evals","optimize","existing skill"]