[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SVB0C5YEQ4FD7ASNYZQK8":3,"skill-same:01M71SVB0C5YEQ4FD7ASNYZQK8":82},{"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":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M71SVB0C5YEQ4FD7ASNYZQK8","using-git-worktrees",null,"Create isolated git worktrees with smart directory selection and safety checks","HigorAlves\u002Forc","HigorAlves","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11262976?v=4","01M71S79EZEMHZ8PQSV0XQJHYY","Higor Alves","01M71S79FKKTCHCN1EDR8DSTWQ",7,"MIT","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\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],"git worktrees","worktrees","git","Using git","using git worktrees","github","with","use","feature","isolation","Safety","directory","plan","work","create","needs","when","implementation plan","superpowers","selection","2026-11-10 13:02:02",false,"---\nname: using-git-worktrees\ndescription: Create isolated git worktrees with smart directory selection and safety checks\nwhen_to_use: Use when starting feature work that needs isolation, or before executing an implementation plan.\nlicense: MIT\nmetadata:\n  author: Jesse Vincent\n  source: Derived from https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers\n---\n\n# Using Git Worktrees\n\n## Overview\n\nGit worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.\n\n**Core principle:** Systematic directory selection + safety verification = reliable isolation.\n\n**Announce at start:** \"I'm using the using-git-worktrees skill to set up an isolated workspace.\"\n\n> [!NOTE]\n> **📋 Harness-managed worktrees land in the pinned location automatically.** orc ships `WorktreeCreate`\u002F`WorktreeRemove` hooks (`hooks\u002Fscripts\u002Fworktree-*.sh`): any worktree Claude Code itself creates (`--worktree`, or an agent with `isolation: worktree`) is placed under `\u003Crepo>\u002F.orc\u002F.worktrees\u002F\u003Csanitized-branch>` and cleaned up only when the tree is clean. This skill's manual process below applies when YOU create the worktree.\n\n## Directory Selection Process\n\n**Iron rule: orc worktrees always live under `.orc\u002F.worktrees\u002F` — at the repo root or, in workspace mode, the workspace root. Never under `$HOME`, never elsewhere.** `.orc\u002F` is always git-ignored in an orc project, so worktree contents can never pollute the tree. There is no \"ask the user where\", no global location, and no CLAUDE.md location override — the location is fixed by design.\n\nExactly two cases:\n\n### Workspace mode\n\nIf the caller sourced `lib\u002Fworkspace-detect.sh` and `ORC_CONTEXT=workspace`, use the workspace-shared trees root, keyed per repo:\n\n```bash\npath=\"$ORC_WORKSPACE_ROOT\u002F.orc\u002F.worktrees\u002F\u003Crepo>\u002F\u003Cbranch>\"\n```\n\nUse this when the caller provides a `repo` + `branch` pair (e.g. from `\u002Forc:start` or `\u002Forc:flow` Phase 4 in workspace mode). Workspace-mode worktrees are always per-repo and always require a target repo — if the caller hasn't passed `repo`, treat it as repo mode for the current repo instead.\n\n### Repo mode (default)\n\nOtherwise use the current repo's own `.orc\u002F.worktrees\u002F`:\n\n```bash\npath=\"$(git rev-parse --show-toplevel)\u002F.orc\u002F.worktrees\u002F\u003Cbranch>\"\n```\n\n## Safety Verification\n\n**MUST confirm `.orc\u002F` is ignored before creating the worktree.** It almost always is (orc scaffolds it into `.gitignore`), but verify — a worktree inside a tracked `.orc\u002F` would get its entire checkout staged.\n\n```bash\n# Workspace mode: check the workspace root; repo mode: check the repo root.\nroot=\"${ORC_WORKSPACE_ROOT:-$(git rev-parse --show-toplevel)}\"\ngit -C \"$root\" check-ignore -q .orc\n```\n\n**If NOT ignored** (non-zero exit), fix it immediately before proceeding:\n1. Append `.orc\u002F` to the root `.gitignore`\n2. Commit that change\n3. Then create the worktree\n\n**Why critical:** Prevents accidentally committing worktree contents to the repository.\n\n## Creation Steps\n\n### 1. Resolve Roots and Branch\n\n```bash\n# Repo mode\nrepo_root=\"$(git rev-parse --show-toplevel)\"\n\n# Workspace mode: the caller supplies $ORC_WORKSPACE_ROOT, $REPO, $BRANCH_NAME.\n# Project name is the explicit `repo` argument (e.g. `api`), NOT derived from\n# git rev-parse (which would lose the workspace context).\n```\n\n### 2. Create Worktree\n\n```bash\n# Determine full path — always under .orc\u002F.worktrees\u002F, never under $HOME\nif [ \"$ORC_CONTEXT\" = \"workspace\" ] && [ -n \"$REPO\" ]; then\n  # Workspace mode: caller supplied $ORC_WORKSPACE_ROOT, $REPO, $BRANCH_NAME\n  path=\"$ORC_WORKSPACE_ROOT\u002F.orc\u002F.worktrees\u002F$REPO\u002F$BRANCH_NAME\"\n  cd \"$ORC_WORKSPACE_ROOT\u002F$REPO\"\nelse\n  # Repo mode: the current repo's own .orc\u002F.worktrees\u002F\n  path=\"$(git rev-parse --show-toplevel)\u002F.orc\u002F.worktrees\u002F$BRANCH_NAME\"\nfi\n\n# Create worktree with new branch\ngit worktree add \"$path\" -b \"$BRANCH_NAME\"\ncd \"$path\"\n```\n\n### 3. Run Project Setup\n\nAuto-detect and run appropriate setup:\n\n```bash\n# Node.js\nif [ -f package.json ]; then npm install; fi\n\n# Rust\nif [ -f Cargo.toml ]; then cargo build; fi\n\n# Python\nif [ -f requirements.txt ]; then pip install -r requirements.txt; fi\nif [ -f pyproject.toml ]; then poetry install; fi\n\n# Go\nif [ -f go.mod ]; then go mod download; fi\n```\n\n### 4. Verify Clean Baseline\n\nRun tests to verify the worktree starts clean:\n\n```bash\n# Examples - use project-appropriate command\nnpm test\ncargo test\npytest\ngo test .\u002F...\n```\n\n**If tests fail:** surface a **⚠️ Caution** callout (baseline tests already failing in the fresh worktree — findings won't be attributable to your change), then ask whether to proceed or investigate.\n\n**If tests pass:** Report ready.\n\n### 5. Report Location\n\n```\nWorktree ready at \u003Cfull-path>\nTests passing (\u003CN> tests, 0 failures)\nReady to implement \u003Cfeature-name>\n```\n\n## Quick Reference\n\nSituation → action table, a worked transcript, and the calling skills: [EXAMPLES.md](references\u002FEXAMPLES.md). Read it on a first run or when a caller passes an unusual repo\u002Fbranch pair.\n\n## Common Mistakes\n\nProblem\u002Ffix pairs: [COMMON-MISTAKES.md](references\u002FCOMMON-MISTAKES.md). Read it when a step fails.\n\n## Red Flags\n## Red Flags\n\n**Never:**\n- Create a worktree anywhere but `.orc\u002F.worktrees\u002F` (repo root or workspace root)\n- Create a worktree under `$HOME`, `.worktrees\u002F`, or a sibling directory\n- Create the worktree without confirming `.orc\u002F` is ignored\n- Skip baseline test verification\n- Proceed with failing tests without asking\n\n**Always:**\n- Place worktrees under `.orc\u002F.worktrees\u002F` — repo root in repo mode, workspace root in workspace mode\n- Confirm `.orc\u002F` is ignored before creating the worktree\n- Auto-detect and run project setup\n- Verify clean test baseline\n","# Using Git Worktrees\n\n## Overview\n\nGit worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.\n\n**Core principle:** Systematic directory selection + safety verification = reliable isolation.\n\n**Announce at start:** \"I'm using the using-git-worktrees skill to set up an isolated workspace.\"\n\n> [!NOTE]\n> **📋 Harness-managed worktrees land in the pinned location automatically.** orc ships `WorktreeCreate`\u002F`WorktreeRemove` hooks (`hooks\u002Fscripts\u002Fworktree-*.sh`): any worktree Claude Code itself creates (`--worktree`, or an agent with `isolation: worktree`) is placed under `\u003Crepo>\u002F.orc\u002F.worktrees\u002F\u003Csanitized-branch>` and cleaned up only when the tree is clean. This skill's manual process below applies when YOU create the worktree.\n\n## Directory Selection Process\n\n**Iron rule: orc worktrees always live under `.orc\u002F.worktrees\u002F` — at the repo root or, in workspace mode, the workspace root. Never under `$HOME`, never elsewhere.** `.orc\u002F` is always git-ignored in an orc project, so worktree contents can never pollute the tree. There is no \"ask the user where\", no global location, and no CLAUDE.md location override — the location is fixed by design.\n\nExactly two cases:\n\n### Workspace mode\n\nIf the caller sourced `lib\u002Fworkspace-detect.sh` and `ORC_CONTEXT=workspace`, use the workspace-shared trees root, keyed per repo:\n\n```bash\npath=\"$ORC_WORKSPACE_ROOT\u002F.orc\u002F.worktrees\u002F\u003Crepo>\u002F\u003Cbranch>\"\n```\n\nUse this when the caller provides a `repo` + `branch` pair (e.g. from `\u002Forc:start` or `\u002Forc:flow` Phase 4 in workspace mode). Workspace-mode worktrees are always per-repo and always require a target repo — if the caller hasn't passed `repo`, treat it as repo mode for the current repo instead.\n\n### Repo mode (default)\n\nOtherwise use the current repo's own `.orc\u002F.worktrees\u002F`:\n\n```bash\npath=\"$(git rev-parse --show-toplevel)\u002F.orc\u002F.worktrees\u002F\u003Cbranch>\"\n```\n\n## Safety Verification\n\n**MUST confirm `.orc\u002F` is ignored before creating the worktree.** It almost always is (orc scaffolds it into `.gitignore`), but verify — a worktree inside a tracked `.orc\u002F` would get its entire checkout staged.\n\n```bash\n# Workspace mode: check the workspace root; repo mode: check the repo root.\nroot=\"${ORC_WORKSPACE_ROOT:-$(git rev-parse --show-toplevel)}\"\ngit -C \"$root\" check-ignore -q .orc\n```\n\n**If NOT ignored** (non-zero exit), fix it immediately before proceeding:\n1. Append `.orc\u002F` to the root `.gitignore`\n2. Commit that change\n3. Then create the worktree\n\n**Why critical:** Prevents accidentally committing worktree contents to the repository.\n\n## Creation Steps\n\n### 1. Resolve Roots and Branch\n\n```bash\n# Repo mode\nrepo_root=\"$(git rev-parse --show-toplevel)\"\n\n# Workspace mode: the caller supplies $ORC_WORKSPACE_ROOT, $REPO, $BRANCH_NAME.\n# Project name is the explicit `repo` argument (e.g. `api`), NOT derived from\n# git rev-parse (which would lose the workspace context).\n```\n\n### 2. Create Worktree\n\n```bash\n# Determine full path — always under .orc\u002F.worktrees\u002F, never under $HOME\nif [ \"$ORC_CONTEXT\" = \"workspace\" ] && [ -n \"$REPO\" ]; then\n  # Workspace mode: caller supplied $ORC_WORKSPACE_ROOT, $REPO, $BRANCH_NAME\n  path=\"$ORC_WORKSPACE_ROOT\u002F.orc\u002F.worktrees\u002F$REPO\u002F$BRANCH_NAME\"\n  cd \"$ORC_WORKSPACE_ROOT\u002F$REPO\"\nelse\n  # Repo mode: the current repo's own .orc\u002F.worktrees\u002F\n  path=\"$(git rev-parse --show-toplevel)\u002F.orc\u002F.worktrees\u002F$BRANCH_NAME\"\nfi\n\n# Create worktree with new branch\ngit worktree add \"$path\" -b \"$BRANCH_NAME\"\ncd \"$path\"\n```\n\n### 3. Run Project Setup\n\nAuto-detect and run appropriate setup:\n\n```bash\n# Node.js\nif [ -f package.json ]; then npm install; fi\n\n# Rust\nif [ -f Cargo.toml ]; then cargo build; fi\n\n# Python\nif [ -f requirements.txt ]; then pip install -r requirements.txt; fi\nif [ -f pyproject.toml ]; then poetry install; fi\n\n# Go\nif [ -f go.mod ]; then go mod download; fi\n```\n\n### 4. Verify Clean Baseline\n\nRun tests to verify the worktree starts clean:\n\n```bash\n# Examples - use project-appropriate command\nnpm test\ncargo test\npytest\ngo test .\u002F...\n```\n\n**If tests fail:** surface a **⚠️ Caution** callout (baseline tests already failing in the fresh worktree — findings won't be attributable to your change), then ask whether to proceed or investigate.\n\n**If tests pass:** Report ready.\n\n### 5. Report Location\n\n```\nWorktree ready at \u003Cfull-path>\nTests passing (\u003CN> tests, 0 failures)\nReady to implement \u003Cfeature-name>\n```\n\n## Quick Reference\n\nSituation → action table, a worked transcript, and the calling skills: [EXAMPLES.md](references\u002FEXAMPLES.md). Read it on a first run or when a caller passes an unusual repo\u002Fbranch pair.\n\n## Common Mistakes\n\nProblem\u002Ffix pairs: [COMMON-MISTAKES.md](references\u002FCOMMON-MISTAKES.md). Read it when a step fails.\n\n## Red Flags\n## Red Flags\n\n**Never:**\n- Create a worktree anywhere but `.orc\u002F.worktrees\u002F` (repo root or workspace root)\n- Create a worktree under `$HOME`, `.worktrees\u002F`, or a sibling directory\n- Create the worktree without confirming `.orc\u002F` is ignored\n- Skip baseline test verification\n- Proceed with failing tests without asking\n\n**Always:**\n- Place worktrees under `.orc\u002F.worktrees\u002F` — repo root in repo mode, workspace root in workspace mode\n- Confirm `.orc\u002F` is ignored before creating the worktree\n- Auto-detect and run project setup\n- Verify clean test baseline\n",{"name":5,"license":15,"metadata":44,"description":7,"when_to_use":47},{"author":45,"source":46},"Jesse Vincent","Derived from https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers","Use when starting feature work that needs isolation, or before executing an implementation plan.","main","7522fd7266944e30052204c2f6df287d8b5516be","orc\u002Fskills\u002Fusing-git-worktrees",0,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc","https:\u002F\u002Forc.novacstack.com\u002F","https:\u002F\u002Fgithub.com\u002FHigorAlves","higoralves.dev","Software Engineering","2026-11-07 07:26:38",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add HigorAlves\u002Forc --skill using-git-worktrees",{"tool":64,"command":65},"bunx","bunx skills add HigorAlves\u002Forc --skill using-git-worktrees",{"tool":67,"command":68},"pnpm","pnpm dlx skills add HigorAlves\u002Forc --skill using-git-worktrees","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",true,[72,78],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002FCOMMON-MISTAKES.md","REFERENCE","参考文档",965,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fusing-git-worktrees\u002Freferences\u002FCOMMON-MISTAKES.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002FEXAMPLES.md",1460,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fusing-git-worktrees\u002Freferences\u002FEXAMPLES.md",[83,118,143,163,184,204],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":102,"publishedAt":39},"01M71SW40F9TAAEDKBYYBCM814","writing-plans","Write a comprehensive implementation plan of bite-sized TDD tasks that an engineer with zero codebase context could execute — exact files, code, tests, and verification steps","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[89,94,99],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":100,"categoryName":101,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000036","内容创作者",[103,104,105,106,37,36,107,35,108,109,110,111,31,112,113,114,115,116,117,26],"writing","writing plans","plans","engineer","files","you","code","tasks","verification","write","steps","context","ZeRO","for","tests",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":129,"publishedAt":39},"01M71SW15KHE4MHJW9NEXV65X2","writing-for-agents","orc's doctrine layer for writing any document an agent consumes — skills, AGENTS.md\u002FCLAUDE.md, reference docs","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[124,125,128],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":126,"categoryName":127,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":100,"categoryName":101,"taxonomyType":97,"taxonomyTypeDesc":98},[130,103,116,131,35,132,133,134,135,136,137,138,26,139,24,140,141,142],"writing for agents","matt pocock","inline","tuning","a skill","layer","doctrine","push","editing","document","https","reference","docs",{"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":150,"publishedAt":39},"01M71SVYQKXT743HHHWGHT3G13","workspace-mode","Use when cwd is a parent dir holding multiple sibling git repos — defines repo auto-detection, --repos\u002F--repo\u002F--all-repos\u002F--this-repo precedence, per-repo dispatch, and linked-PR mechanics.","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fworkspace-mode\u002FSKILL.md",[149],{"categoryNo":126,"categoryName":127,"taxonomyType":92,"taxonomyTypeDesc":93},[151,152,153,154,155,35,156,21,157,158,26,159,160,161,162],"workspace mode","mode","workspace","mechanics","auto","repos","pr","repo","dispatch","auto-detection","detection","parent",{"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":170,"publishedAt":39},"01M71SVVP3BXS06G9395P2K0RH","wizard","Generate an interactive bash wizard walking a human through work only they can perform — credentials, secrets, one-off migrations","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwizard\u002FSKILL.md",[169],{"categoryNo":126,"categoryName":127,"taxonomyType":92,"taxonomyTypeDesc":93},[165,171,172,173,174,131,35,175,32,176,177,178,179,113,180,181,116,26,182,183],"condition","never","provisioning infrastructure","only","Bash","credentials","generate","human","secrets","infrastructure","do","one","interactive",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":39},"01M71SVT4AR6NKAM5B077E7QSJ","wait-what","Stop and re-pitch — the last message did not land; say it again simply, in the project's own vocabulary.","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[191,192,193,194,195,131,196,197,198,199,24,140,200,201,202,203],"wait what","wait","project","re","true","pitch","last","say","message","land","it","stop","vocabulary",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":214,"publishedAt":39},"01M71SVQVYRA9QBQ6G8MWR8G6F","vitest","Vitest fast unit testing framework powered by Vite with Jest-compatible API","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fvitest\u002FSKILL.md",[210,213],{"categoryNo":211,"categoryName":212,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},[206,215,216,217,218,219,103,35,220,221,222,223,224,225,226,227,228,229,117,230],"coverage","unit","testing","testing framework","generated","api","jest","2026","at","scripts","unit testing","antfu","framework","vite","mocking","dev"]