[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QJ7ZZKYJYVWESVYDYNAPT7":3,"skill-same:01M6QJ7ZZKYJYVWESVYDYNAPT7":80},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":13,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6QJ7ZZKYJYVWESVYDYNAPT7","cross-branch-fix-porter",null,"Cross-branch fix porting expert. Understands fix intent and re-implements the same fix goal in the current branch's code context when direct cherry-pick isn't feasible. Should be used when the user needs to apply a fix from one branch to another where code structures differ significantly. Distinguished from feature-port-doc-generator which documents changes, this skill actively re-implements fixes.","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\u002Fcross-branch-fix-porter\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"porter","cross branch fix porter","fix","branch","pick","dev","code","expert","branches","feature","documents","generator","re","dev-tools","which","for","fixes","apply","porting","teams","2026-11-10 10:12:30",false,"---\nname: cross-branch-fix-porter\ndescription: >-\n  Cross-branch fix porting expert. Understands fix intent and re-implements the same fix goal in the current branch's\n  code context when direct cherry-pick isn't feasible.\n  Should be used when the user needs to apply a fix from one branch to another where code structures differ\n  significantly.\n  Distinguished from feature-port-doc-generator which documents changes, this skill actively re-implements fixes.\ncategory: dev-tools\nboundary:\n  vs_feature-port-doc-generator: \"feature-port-doc-generator documents changes for other teams, this skill actively re-implements fixes across branches\"\n---\n\n# Cross-Branch Fix Porting\n\n## Core Approach\n\n**Don't copy code — copy intent.** First understand what problem the fix solves and why it was done that way, then re-implement the same fix goal within the current branch's code logic.\n\n## When to Use\n\n- User provides a commit ID that needs to be ported to the current branch\n- Two projects have significantly different structures (different frameworks, different directory layouts)\n- Direct cherry-pick would produce many conflicts or logical errors\n\n## Workflow\n\n### Phase 1: Get Fix 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. Analyze diff, extract fix intent\n```\n\n**Case B: From conversation context**\n\n```\n1. Search conversation history for fix-related content\n2. Extract already-analyzed fix content and intent\n```\n\n### Phase 2: Analyze Fix Intent\n\nAfter reading the diff, answer these questions:\n\n```\n1. [Root cause] What bug did this fix solve, or what requirement did it fulfill?\n2. [Change scope] Which files are involved? What's the purpose of each file's change?\n3. [Core logic] What's the key behavioral change (not code change)?\n4. [Dependencies] Does the fix depend on specific utility functions, components, or type definitions?\n```\n\n### Phase 3: Locate Corresponding Files in Current Branch\n\n```\n1. Based on the functional modules involved in the fix, search for corresponding files in the current branch\n2. Read candidate file contents to confirm they handle the same functionality\n3. If no corresponding file is found, inform the user and explain why\n```\n\n### Phase 4: Determine if Direct Copy is Possible\n\nDirect copy is only appropriate when **all** of these conditions are met:\n\n1. The file in the original commit diff is marked as \"new file\" (entirely new creation)\n2. No file at the same path or with the same functionality exists in the current branch\n3. The file content doesn't depend on modules or types that don't exist in the current branch\n\nIf conditions are met: copy the file directly.\nIf not: proceed to Phase 5.\n\n### Phase 5: Re-implement the Fix\n\n**Use the current branch's logic as the source of truth.** Don't copy the original code:\n\n```\n1. Read the current branch's corresponding file's complete logic\n2. Understand the current branch's code style, encapsulation patterns, utility functions\n3. \"Translate\" the fix intent into the current branch's implementation style\n4. If the current branch already has similar logic, modify it in place\n```\n\n**Porting principles:**\n\n| Principle                 | Description                                                          |\n| ------------------------- | -------------------------------------------------------------------- |\n| **Intent first**          | Reproduce the behavioral effect of the fix, not the code             |\n| **Respect current style** | Use the current branch's utility functions, types, and encapsulation |\n| **Minimal change**        | Only modify what's necessary, don't introduce unrelated changes      |\n| **Consistency**           | Match the current branch's code style and conventions                |\n\n---\n\n## Output Report\n\n```markdown\n## Cross-Branch Fix Porting Report\n\n### Fix Intent Summary\n\n[One-sentence description of the problem the fix solves]\n\n### File Mapping\n\n| Original fix file | Current branch file | Handling       |\n| ----------------- | ------------------- | -------------- |\n| src\u002Fa.ts          | src\u002Fb.ts            | Re-implemented |\n| src\u002Fnew.ts        | —                   | Direct copy    |\n\n### Key Differences\n\n[Structural differences, implementation differences]\n\n### Applied Changes\n\n- [Change 1]\n- [Change 2]\n\n### Items Requiring User Confirmation (if any)\n\n- [Confirmation item]\n```\n\n---\n\n## Important Notes\n\n- **Don't blindly copy code** — Original code may depend on utility functions or types that don't exist in the current branch\n- **Analyze before acting** — Complete intent analysis before modifying any files\n- **Ask when uncertain** — If the intent of a change is ambiguous, confirm with the user\n- **Go step by step for large structural differences** — Port core logic first, then handle edge cases\n","# Cross-Branch Fix Porting\n\n## Core Approach\n\n**Don't copy code — copy intent.** First understand what problem the fix solves and why it was done that way, then re-implement the same fix goal within the current branch's code logic.\n\n## When to Use\n\n- User provides a commit ID that needs to be ported to the current branch\n- Two projects have significantly different structures (different frameworks, different directory layouts)\n- Direct cherry-pick would produce many conflicts or logical errors\n\n## Workflow\n\n### Phase 1: Get Fix 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. Analyze diff, extract fix intent\n```\n\n**Case B: From conversation context**\n\n```\n1. Search conversation history for fix-related content\n2. Extract already-analyzed fix content and intent\n```\n\n### Phase 2: Analyze Fix Intent\n\nAfter reading the diff, answer these questions:\n\n```\n1. [Root cause] What bug did this fix solve, or what requirement did it fulfill?\n2. [Change scope] Which files are involved? What's the purpose of each file's change?\n3. [Core logic] What's the key behavioral change (not code change)?\n4. [Dependencies] Does the fix depend on specific utility functions, components, or type definitions?\n```\n\n### Phase 3: Locate Corresponding Files in Current Branch\n\n```\n1. Based on the functional modules involved in the fix, search for corresponding files in the current branch\n2. Read candidate file contents to confirm they handle the same functionality\n3. If no corresponding file is found, inform the user and explain why\n```\n\n### Phase 4: Determine if Direct Copy is Possible\n\nDirect copy is only appropriate when **all** of these conditions are met:\n\n1. The file in the original commit diff is marked as \"new file\" (entirely new creation)\n2. No file at the same path or with the same functionality exists in the current branch\n3. The file content doesn't depend on modules or types that don't exist in the current branch\n\nIf conditions are met: copy the file directly.\nIf not: proceed to Phase 5.\n\n### Phase 5: Re-implement the Fix\n\n**Use the current branch's logic as the source of truth.** Don't copy the original code:\n\n```\n1. Read the current branch's corresponding file's complete logic\n2. Understand the current branch's code style, encapsulation patterns, utility functions\n3. \"Translate\" the fix intent into the current branch's implementation style\n4. If the current branch already has similar logic, modify it in place\n```\n\n**Porting principles:**\n\n| Principle                 | Description                                                          |\n| ------------------------- | -------------------------------------------------------------------- |\n| **Intent first**          | Reproduce the behavioral effect of the fix, not the code             |\n| **Respect current style** | Use the current branch's utility functions, types, and encapsulation |\n| **Minimal change**        | Only modify what's necessary, don't introduce unrelated changes      |\n| **Consistency**           | Match the current branch's code style and conventions                |\n\n---\n\n## Output Report\n\n```markdown\n## Cross-Branch Fix Porting Report\n\n### Fix Intent Summary\n\n[One-sentence description of the problem the fix solves]\n\n### File Mapping\n\n| Original fix file | Current branch file | Handling       |\n| ----------------- | ------------------- | -------------- |\n| src\u002Fa.ts          | src\u002Fb.ts            | Re-implemented |\n| src\u002Fnew.ts        | —                   | Direct copy    |\n\n### Key Differences\n\n[Structural differences, implementation differences]\n\n### Applied Changes\n\n- [Change 1]\n- [Change 2]\n\n### Items Requiring User Confirmation (if any)\n\n- [Confirmation item]\n```\n\n---\n\n## Important Notes\n\n- **Don't blindly copy code** — Original code may depend on utility functions or types that don't exist in the current branch\n- **Analyze before acting** — Complete intent analysis before modifying any files\n- **Ask when uncertain** — If the intent of a change is ambiguous, confirm with the user\n- **Go step by step for large structural differences** — Port core logic first, then handle edge cases\n",{"name":5,"boundary":48,"category":36,"description":7},{"vs_feature-port-doc-generator":49},"feature-port-doc-generator documents changes for other teams, this skill actively re-implements fixes across branches","main","b9a52d8e27455bdad953d64928696d028223ea1b","skills\u002Fdev-tools\u002Fcross-branch-fix-porter","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager","https:\u002F\u002Fgithub.com\u002FImaginerLabs","2026-04-18 16:27:13",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add ImaginerLabs\u002Fskill-manager --skill cross-branch-fix-porter",{"tool":62,"command":63},"bunx","bunx skills add ImaginerLabs\u002Fskill-manager --skill cross-branch-fix-porter",{"tool":65,"command":66},"pnpm","pnpm dlx skills add ImaginerLabs\u002Fskill-manager --skill cross-branch-fix-porter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Fcross-branch-fix-porter\u002FSKILL.md",true,[70,76],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fanalysis-template.md","REFERENCE","参考文档",3920,"https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Fcross-branch-fix-porter\u002Freferences\u002Fanalysis-template.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fworkflow.md",7785,"https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Fcross-branch-fix-porter\u002Freferences\u002Fworkflow.md",[81,111,131,159,194,219],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":93,"publishedAt":43},"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",[87,88],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[94,95,96,97,98,99,100,101,102,103,83,50,104,105,106,107,108,109,110,38],"meeting minutes","meeting","minutes","writing","github","copilot","generate","decisions","meetings","up","agenda","actionable","concise","follow-up","tree","true","action",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":43},"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",[],[118,119,120,97,98,99,121,122,123,124,30,125,50,126,127,128,129,108,109,130],"documentation","documentation writer","writer","https","quality","technical","technical writer","documentation expert","structure","authoring","software","principles","high",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":144,"publishedAt":43},"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",[137,140,141],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":142,"categoryName":143,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000036","内容创作者",[145,146,97,147,148,118,149,150,151,152,153,154,50,155,156,127,157,158,108,38],"doc coauthoring","doc","workflow","official","tasks","decision","write","context","proposals","guide","refine","iteration","trigger","co",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":175,"publishedAt":43},"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",[165,168,171,172],{"categoryNo":166,"categoryName":167,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":173,"categoryName":174,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000030","开发工程师",[176,177,147,29,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193],"code review","review","code review workflow","testing","frontend","test","change","code quality","code-review","analysis","check","coverage","quality check","basic","multi","comprehensive code review","with","phase",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":209,"publishedAt":43},"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",[200,201,204,205,206],{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":202,"categoryName":203,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":173,"categoryName":174,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":207,"categoryName":208,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000032","设计师",[181,182,29,210,211,179,212,213,147,214,184,215,187,216,50,217,218,37,38,193],"designer","code change test designer","design","diffs","commit","edge","diff","tests","flows",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":226,"publishedAt":43},"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",[225],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[227,228,229,230,148,231,232,233,234,235,185,236,237,238,50,239,240,108,38,221],"skill creator","creator","performance","run evals","variance analysis","create","run","benchmark","Meta","improve","edit","evals","optimize","existing skill"]