[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GGSJ6HD2DFVZQTESJ81GYM":3,"skill-same:01M6GGSJ6HD2DFVZQTESJ81GYM":65},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6GGSJ6HD2DFVZQTESJ81GYM","using-git-worktrees",null,"When running long feature implementations, parallel branch work, or build\u002Ftest scripts that must not interfere with the user's active working directory. Creates isolated execution environments via git worktrees in sibling directories.","ahmadulhoq\u002Fagentskel","ahmadulhoq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3884252?v=4","01M6GGC32SQTQ52FY4JB14FYSY","Ahmadul Hoq","01M6GGC37CJEYM63V3WEHY4Y8V",13,"MIT","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"using git worktrees","git","Using git","git worktrees","worktrees","build","directories","environments","with","via","long","scripts","feature","active","directory","branch","work","parallel","execution","test","2026-11-10 10:12:30",false,"---\nname: using-git-worktrees\nlicense: MIT\ndescription: When running long feature implementations, parallel branch work, or build\u002Ftest scripts that must not interfere with the user's active working directory. Creates isolated execution environments via git worktrees in sibling directories.\n---\n\n# Using Git Worktrees Skill\n\n**Purpose:** Keep the active repo clean. Work happens in a sibling directory — no nested git repos, no IDE re-indexing loops.\n\n## When to Use\n| Situation | Use worktree? |\n|-----------|--------------|\n| Long feature run (> ~30 min) | Yes |\n| Parallel branch comparison | Yes |\n| Running full build\u002Ftest suite against a branch | Yes |\n| Quick hotfix or single-file change | No — use normal branch |\n\n## Setup\n1. Confirm the feature branch exists (created by `git-flow` before any code):\n   ```bash\n   BRANCH=\u003Cbranch-name>\n   REPO=$(basename $(git rev-parse --show-toplevel))\n   WORKTREE_PATH=\"..\u002F${REPO}-${BRANCH}\"\n   ```\n2. Create the worktree:\n   ```bash\n   git worktree add \"$WORKTREE_PATH\" \"$BRANCH\"\n   ```\n3. Enter the worktree before running any build or test commands:\n   ```bash\n   cd \"$WORKTREE_PATH\"\n   ```\n4. All implementation, build, and test commands execute inside `$WORKTREE_PATH`.\n   The main repo directory is effectively read-only during this session.\n\n## Rules\n- **Sibling directories only.** Never place a worktree inside the repo (e.g., `.\u002Fworktrees\u002F`). Nested paths cause IDE indexing loops and nested-git errors.\n- One worktree per branch. Do not create multiple worktrees for the same branch.\n- Do not edit files in the main repo directory while a worktree session is active.\n\n## Cleanup (after PR is merged)\n5. Return to main repo directory, then:\n   ```bash\n   git worktree remove \"$WORKTREE_PATH\"\n   git branch -d \"$BRANCH\"   # only after merge is confirmed\n   ```\n\n---\n\n**Gate:** Do not run build or test scripts in the main repo directory when a worktree\nexists for the active branch.\n","# Using Git Worktrees Skill\n\n**Purpose:** Keep the active repo clean. Work happens in a sibling directory — no nested git repos, no IDE re-indexing loops.\n\n## When to Use\n| Situation | Use worktree? |\n|-----------|--------------|\n| Long feature run (> ~30 min) | Yes |\n| Parallel branch comparison | Yes |\n| Running full build\u002Ftest suite against a branch | Yes |\n| Quick hotfix or single-file change | No — use normal branch |\n\n## Setup\n1. Confirm the feature branch exists (created by `git-flow` before any code):\n   ```bash\n   BRANCH=\u003Cbranch-name>\n   REPO=$(basename $(git rev-parse --show-toplevel))\n   WORKTREE_PATH=\"..\u002F${REPO}-${BRANCH}\"\n   ```\n2. Create the worktree:\n   ```bash\n   git worktree add \"$WORKTREE_PATH\" \"$BRANCH\"\n   ```\n3. Enter the worktree before running any build or test commands:\n   ```bash\n   cd \"$WORKTREE_PATH\"\n   ```\n4. All implementation, build, and test commands execute inside `$WORKTREE_PATH`.\n   The main repo directory is effectively read-only during this session.\n\n## Rules\n- **Sibling directories only.** Never place a worktree inside the repo (e.g., `.\u002Fworktrees\u002F`). Nested paths cause IDE indexing loops and nested-git errors.\n- One worktree per branch. Do not create multiple worktrees for the same branch.\n- Do not edit files in the main repo directory while a worktree session is active.\n\n## Cleanup (after PR is merged)\n5. Return to main repo directory, then:\n   ```bash\n   git worktree remove \"$WORKTREE_PATH\"\n   git branch -d \"$BRANCH\"   # only after merge is confirmed\n   ```\n\n---\n\n**Gate:** Do not run build or test scripts in the main repo directory when a worktree\nexists for the active branch.\n",{"name":5,"license":15,"description":7},"main","d94c109a4fad51623dc6048315860e53b32673fb","roles\u002Fdev\u002Fskills\u002Fusing-git-worktrees",3,"https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel","https:\u002F\u002Fgithub.com\u002Fahmadulhoq","2026-11-07 00:53:22",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add ahmadulhoq\u002Fagentskel --skill using-git-worktrees",{"tool":57,"command":58},"bunx","bunx skills add ahmadulhoq\u002Fagentskel --skill using-git-worktrees",{"tool":60,"command":61},"pnpm","pnpm dlx skills add ahmadulhoq\u002Fagentskel --skill using-git-worktrees","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",true,[],[66,86,112,137,151,177],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":39},"01M6GGSN2D57Y8BR50X08Y695H","setup-project","When setting up agentskel on a new project that does not yet have .memory\u002F or .agents\u002F. Use when the user says \"set up agentskel\", \"install agentskel\", or \"add agent memory to this project\".","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Fskills\u002Fsetup-project\u002FSKILL.md",[],[73,74,75,76,77,78,79,80,81,82,83,84,85],"setup project","project","setup","new project","add","up","use","install","add agent","user","SET","agent memory","memory",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":97,"publishedAt":39},"01M6GGSCFPK7MDSZH96XTNZR9B","test-engineer","When designing test strategy, analysing coverage, or writing tests outside the TDD cycle. Also use when working with CI pipelines or validating changes end-to-end.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Ftest-engineer\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[98,99,38,100,101,102,79,103,104,105,106,107,108,109,27,110,111],"test engineer","engineer","writing tests","test strategy","pipelines","coverage","strategy","ci","tdd cycle","tdd","writing","cycle","end","tests",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":122,"publishedAt":39},"01M6GGS8YA9XZB6DWV22JC0YTB","test-driven-development","When implementing logic changes during develop-feature or implement-task. Use the Red-Green-Refactor cycle to write a failing test before any production code.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[118,121],{"categoryNo":119,"categoryName":120,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[123,124,125,38,126,31,127,128,129,130,79,131,132,133,134,135,109,136],"development","driven","test driven development","red","logic","green","task","red-green-refactor","write","develop","refactor","Production","code","implement",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":39},"01M6GGS61D41ZJG4D8XAS97H62","task-planner","When decomposing a feature or spec into implementable subtasks, estimating scope, or orchestrating multi-step work across subagents.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Ftask-planner\u002FSKILL.md",[],[144,129,145,35,146,147,148,149,31,150],"task planner","planner","spec","subagents","multi","scope","across",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":39},"01M6GGS30NJW4Q7QN4KVT0CV08","systematic-debugger","When applying debugging techniques during any investigation — root cause tracing, bisect, defense-in-depth. Enforces hypothesis-first analysis and prohibits guess-and-check changes. Use standalone or inside the debug-issue workflow.","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Fsystematic-debugger\u002FSKILL.md",[],[158,159,160,161,162,163,164,165,166,167,79,168,169,170,171,172,173,174,175,176],"systematic debugger","systematic","debugger","issue","debug","debugging","standalone","root","tracing","issue workflow","check","bisect","investigation","analysis","defense-in-depth","first","defense","hypothesis","workflow",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":39},"01M6GGS04EDQVVJRW5CTB3V60K","domain-expert","When working on features that require domain knowledge — business rules, terminology, or invariants specific to this project. [Replace this description and the content below with your project's domain.]","https:\u002F\u002Fgithub.com\u002Fahmadulhoq\u002Fagentskel\u002Fblob\u002Fmain\u002Froles\u002Fdev\u002Fskills\u002Fdomain-expert\u002FSKILL.md",[],[184,185,186,187,74,188,189,190,191,27,192],"expert","domain expert","domain","terminology","knowledge","Rules","business","content","invariants"]