worktree
Use for non-trivial or parallel work that should happen in a separate git worktree.
它会碰到什么
这一栏是扫描器报的事实，不是结论。命中多不等于有毒（安全工具、规则库、示例脚本本来就会包含危险写法），命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系，需要你自己看。
技能内容
Worktree
If topology=multi-module (triage announcement or coordinator spec/plan declaration), read ../references/multi-module.md. Treat each repository as an independent Git and worktree boundary; never run a workspace-wide Git mutation from their common parent.
Before creating worktrees, resolve each registered repository and verify status and baseline. Map paths in the coordinator plan and use the change-set ID in names. A missing repo, unrelated dirty change, or red baseline blocks the change. Detached HEAD is allowed for read-only integration, not implementation. Do not clone or clean automatically.
git worktree add ../<repo>-<topic> -b <type>/<topic> # <type>: feat | fix | chore | ...
cd ../<repo>-<topic> && <setup> && <run tests>Baseline must be green in every participating repository. If red, STOP - don't build on broken ground. Done → ship.
Tool scope
Worktrees are separate directories from the main repo. Semantic indexing (code graph, symbol search) covers the original repo, not the worktree. File tools (read, grep, glob) work normally. For short-lived worktrees this is acceptable; for long sessions, note this limitation to the agent at dispatch.
想直接用这个技能？
本站把开放许可（MIT / Apache 等）的技能按仓库打包整理到网盘，点一下转存到你自己的网盘，不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接，不打包。
它属于哪个仓库
plugins/ouonet/praxis/skills/worktree/SKILL.md