[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A8AM1CVHG4DC1HZ2DMPY6B":3,"skill-same:01M7A8AM1CVHG4DC1HZ2DMPY6B":50},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M7A8AM1CVHG4DC1HZ2DMPY6B","git-worktree",null,"Use git worktrees to run multiple coding agents in parallel on one repo without collisions. Use when starting a task in a shared repo, when the user says \"worktree\", \"parallel agents\", \"one worktree per task\", or when agents keep overwriting each other's changes. Covers creating worktrees, making them as complete as the main checkout (.env files, dependencies, databases, ports), merging back, and cleanup.","Rabot-Dutilleul\u002FFabien-skills","Rabot-Dutilleul","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F310605036?v=4","01M7A89F6Q9N1A7VJAQ85M1QY7","01M7A89F7N008SM2BX81BCSEH9",1,"MIT","https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fgit-worktree\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: git-worktree\ndescription: Use git worktrees to run multiple coding agents in parallel on one repo without collisions. Use when starting a task in a shared repo, when the user says \"worktree\", \"parallel agents\", \"one worktree per task\", or when agents keep overwriting each other's changes. Covers creating worktrees, making them as complete as the main checkout (.env files, dependencies, databases, ports), merging back, and cleanup.\ndisable-model-invocation: true\n---\n\n# Git Worktrees for Parallel Agents\n\n## Start here (before any task work)\n\nDetect where you are:\n\n```bash\n[ \"$(git rev-parse --path-format=absolute --git-dir)\" = \"$(git rev-parse --path-format=absolute --git-common-dir)\" ] \\\n  && echo \"primary checkout\" || echo \"worktree\"\n```\n\n- **Primary checkout** → do NOT start editing here. Create a worktree named after the task, bootstrap it (see \"Making the worktree complete\"), `cd` into it, and do ALL task work there.\n- **Worktree** (e.g. Cursor already started you in one) → proceed with the task.\n\n## What a worktree is\n\nOne repo, multiple folders. `git worktree add` creates an extra checkout of the same repository in a separate directory, on its own branch. All worktrees share one `.git` history, but each has its own files. Two agents in two worktrees physically cannot overwrite each other's work.\n\n## The working model\n\n- **One task = one worktree = one agent session.** Never let two agents share a working directory.\n- **The primary checkout is the integration point.** It stays on the main branch and is used only to review, merge, and push. It is not a scratchpad.\n- **Nothing auto-merges.** The human reviews each worktree's diff, then merges it into main (or discards it), then deletes the worktree.\n- **Worktree branches are local and short-lived.** Never push them unless the user explicitly asks. Only main gets pushed.\n- Merge one worktree at a time. Rebase a stale worktree onto main before merging if main moved.\n\n## Creating and removing\n\n```bash\ngit worktree add ..\u002Fmyrepo-task-x          # new worktree + branch \"myrepo-task-x\"\ngit worktree add ..\u002Ffix-y -b fix-y main    # explicit branch off main\ngit worktree list                          # see all worktrees\ngit worktree remove ..\u002Fmyrepo-task-x       # delete when merged\u002Fabandoned\ngit worktree prune                         # clean up stale registrations\n```\n\nNote: a branch can only be checked out in ONE worktree at a time (including main).\n\nIn Cursor: start agents in worktrees via the Agents Window, or `\u002Fworktree \u003Ctask>` in a chat. `\u002Fapply-worktree` merges the result into your main checkout; `\u002Fdelete-worktree` discards; `\u002Fbest-of-n model1,model2 \u003Ctask>` runs the same task in parallel worktrees, one per model. Cursor auto-deletes older worktrees (default cap 25 per machine), so merge or push results promptly.\n\n## Making the worktree complete\n\nA fresh worktree contains ONLY tracked files. Everything gitignored is missing. An agent dropped into a bare worktree will fail confusingly, so replicate:\n\n1. **Env\u002Fsecret files** — copy `.env`, `.env.local`, and similar from the primary checkout. Copy, never symlink (an agent editing a symlinked env file would corrupt the original).\n2. **Dependencies** — run the install (`npm ci`, `pnpm install`, `uv sync`, `bundle install`). Never symlink `node_modules`; it breaks builds in both checkouts.\n3. **Local databases and services** — decide per service:\n   - Shared server (e.g. one Postgres container): pin the identity so worktrees don't spawn duplicates fighting over the same port. For Docker Compose, set a top-level `name:` in the compose file — otherwise the project name comes from the folder name and every worktree starts its own container on the same port.\n   - Per-worktree state (e.g. SQLite files): copy or re-seed it.\n4. **Ports** — dev servers, test servers, and debuggers bind fixed ports. Either run one at a time across all worktrees, or make the port configurable per worktree.\n5. **Generated files and caches** — rebuild in the worktree (`npm run build`, codegen); build output is gitignored and won't be there.\n6. **Git hooks** — `core.hooksPath` and `.git\u002Fconfig` are shared across worktrees automatically; verify hook scripts don't assume the primary checkout's path.\n\n## Automate the setup\n\nCodify the checklist so every worktree bootstraps itself. In Cursor, `.cursor\u002Fworktrees.json` runs on worktree creation (`$ROOT_WORKTREE_PATH` = the primary checkout):\n\n```json\n{\n  \"setup-worktree\": [\n    \"npm ci\",\n    \"cp $ROOT_WORKTREE_PATH\u002F.env.local .env.local\"\n  ]\n}\n```\n\nWithout Cursor, keep a `scripts\u002Fsetup-worktree.sh` in the repo and run it as the first command in any new worktree. Inside a worktree, the primary checkout's path is:\n\n```bash\ndirname \"$(git rev-parse --path-format=absolute --git-common-dir)\"\n```\n\n## Merging back\n\n```bash\n# from the primary checkout, after reviewing the worktree's diff:\ngit merge --no-ff task-branch     # or: git merge --squash task-branch\ngit worktree remove ..\u002Fmyrepo-task-x\ngit branch -d task-branch\n```\n\nOr in Cursor, simply `\u002Fapply-worktree` from the agent's chat, review, commit.\n\n## Gotchas\n\n- Gitignored files silently missing is the #1 failure — always bootstrap before the agent starts.\n- Disk: each worktree duplicates the working files plus its own `node_modules`. Delete merged worktrees; don't hoard them.\n- Long-lived worktrees rot. If a task stalls for days, rebase onto main or restart it.\n- Uncommitted work in a deleted worktree is gone. Commit in the worktree early and often; the commits live in the shared repo even after the folder is removed.\n- One shared stash list, one shared config, one shared refs namespace — worktrees isolate files, not git state.\n","# Git Worktrees for Parallel Agents\n\n## Start here (before any task work)\n\nDetect where you are:\n\n```bash\n[ \"$(git rev-parse --path-format=absolute --git-dir)\" = \"$(git rev-parse --path-format=absolute --git-common-dir)\" ] \\\n  && echo \"primary checkout\" || echo \"worktree\"\n```\n\n- **Primary checkout** → do NOT start editing here. Create a worktree named after the task, bootstrap it (see \"Making the worktree complete\"), `cd` into it, and do ALL task work there.\n- **Worktree** (e.g. Cursor already started you in one) → proceed with the task.\n\n## What a worktree is\n\nOne repo, multiple folders. `git worktree add` creates an extra checkout of the same repository in a separate directory, on its own branch. All worktrees share one `.git` history, but each has its own files. Two agents in two worktrees physically cannot overwrite each other's work.\n\n## The working model\n\n- **One task = one worktree = one agent session.** Never let two agents share a working directory.\n- **The primary checkout is the integration point.** It stays on the main branch and is used only to review, merge, and push. It is not a scratchpad.\n- **Nothing auto-merges.** The human reviews each worktree's diff, then merges it into main (or discards it), then deletes the worktree.\n- **Worktree branches are local and short-lived.** Never push them unless the user explicitly asks. Only main gets pushed.\n- Merge one worktree at a time. Rebase a stale worktree onto main before merging if main moved.\n\n## Creating and removing\n\n```bash\ngit worktree add ..\u002Fmyrepo-task-x          # new worktree + branch \"myrepo-task-x\"\ngit worktree add ..\u002Ffix-y -b fix-y main    # explicit branch off main\ngit worktree list                          # see all worktrees\ngit worktree remove ..\u002Fmyrepo-task-x       # delete when merged\u002Fabandoned\ngit worktree prune                         # clean up stale registrations\n```\n\nNote: a branch can only be checked out in ONE worktree at a time (including main).\n\nIn Cursor: start agents in worktrees via the Agents Window, or `\u002Fworktree \u003Ctask>` in a chat. `\u002Fapply-worktree` merges the result into your main checkout; `\u002Fdelete-worktree` discards; `\u002Fbest-of-n model1,model2 \u003Ctask>` runs the same task in parallel worktrees, one per model. Cursor auto-deletes older worktrees (default cap 25 per machine), so merge or push results promptly.\n\n## Making the worktree complete\n\nA fresh worktree contains ONLY tracked files. Everything gitignored is missing. An agent dropped into a bare worktree will fail confusingly, so replicate:\n\n1. **Env\u002Fsecret files** — copy `.env`, `.env.local`, and similar from the primary checkout. Copy, never symlink (an agent editing a symlinked env file would corrupt the original).\n2. **Dependencies** — run the install (`npm ci`, `pnpm install`, `uv sync`, `bundle install`). Never symlink `node_modules`; it breaks builds in both checkouts.\n3. **Local databases and services** — decide per service:\n   - Shared server (e.g. one Postgres container): pin the identity so worktrees don't spawn duplicates fighting over the same port. For Docker Compose, set a top-level `name:` in the compose file — otherwise the project name comes from the folder name and every worktree starts its own container on the same port.\n   - Per-worktree state (e.g. SQLite files): copy or re-seed it.\n4. **Ports** — dev servers, test servers, and debuggers bind fixed ports. Either run one at a time across all worktrees, or make the port configurable per worktree.\n5. **Generated files and caches** — rebuild in the worktree (`npm run build`, codegen); build output is gitignored and won't be there.\n6. **Git hooks** — `core.hooksPath` and `.git\u002Fconfig` are shared across worktrees automatically; verify hook scripts don't assume the primary checkout's path.\n\n## Automate the setup\n\nCodify the checklist so every worktree bootstraps itself. In Cursor, `.cursor\u002Fworktrees.json` runs on worktree creation (`$ROOT_WORKTREE_PATH` = the primary checkout):\n\n```json\n{\n  \"setup-worktree\": [\n    \"npm ci\",\n    \"cp $ROOT_WORKTREE_PATH\u002F.env.local .env.local\"\n  ]\n}\n```\n\nWithout Cursor, keep a `scripts\u002Fsetup-worktree.sh` in the repo and run it as the first command in any new worktree. Inside a worktree, the primary checkout's path is:\n\n```bash\ndirname \"$(git rev-parse --path-format=absolute --git-common-dir)\"\n```\n\n## Merging back\n\n```bash\n# from the primary checkout, after reviewing the worktree's diff:\ngit merge --no-ff task-branch     # or: git merge --squash task-branch\ngit worktree remove ..\u002Fmyrepo-task-x\ngit branch -d task-branch\n```\n\nOr in Cursor, simply `\u002Fapply-worktree` from the agent's chat, review, commit.\n\n## Gotchas\n\n- Gitignored files silently missing is the #1 failure — always bootstrap before the agent starts.\n- Disk: each worktree duplicates the working files plus its own `node_modules`. Delete merged worktrees; don't hoard them.\n- Long-lived worktrees rot. If a task stalls for days, rebase onto main or restart it.\n- Uncommitted work in a deleted worktree is gone. Commit in the worktree early and often; the commits live in the shared repo even after the folder is removed.\n- One shared stash list, one shared config, one shared refs namespace — worktrees isolate files, not git state.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","04169bc4a9e84756830a49d8d32924c0271fb7b8","engineering\u002Fgit-worktree",0,"https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills","https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul","2026-10-29 02:42:27",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Rabot-Dutilleul\u002FFabien-skills --skill git-worktree",{"tool":37,"command":38},"bunx","bunx skills add Rabot-Dutilleul\u002FFabien-skills --skill git-worktree",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Rabot-Dutilleul\u002FFabien-skills --skill git-worktree","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fgit-worktree\u002FSKILL.md",[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fgit-worktree\u002Fagents\u002Fopenai.yaml",[51,58,64,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7A8G562266H8YP52SBC78W3","anti-sleep","Keep the Windows machine awake from WSL for a set duration or while a process runs.","https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills\u002Fblob\u002Fmain\u002Fwindows&bash-tools\u002Fanti-sleep\u002FSKILL.md",[],[],{"skillNo":59,"name":53,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M7A8G1N88NTM165JVE1X3ZVT","Keep the user's MacBook awake reliably with macOS caffeinate for a set duration or while a process runs. Use for \"don't let my Mac sleep\", \"keep the screen on\", \"anti-sleep\", \"caffeinate\", overnight work, or long builds. Unlike a normal background job, it survives temporary agent-shell cleanup.","https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills\u002Fblob\u002Fmain\u002Fwindows&bash-tools\u002Fanti-sleep\u002F.macos-original\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7A8FWZSHXW5HHQS8JM7WVZY","security-audit","Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full\u002Fcomprehensive\u002Fend-to-end reviews, or requested report artifacts.","https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills\u002Fblob\u002Fmain\u002Fsecurity\u002Fsecurity-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills\u002Fblob\u002Fmain\u002Fsecurity\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7A8FPEKRZWEX0SM6DR1F1DQ","storm-research","Use when someone asks to run Storm Research, use the storm-research skill, run the STORM method on a topic, says \"storm research this\" \u002F \"storm report on X\" \u002F \"give me a STORM briefing on X\", or wants a multi-perspective, citation-verified HTML research briefing on a topic. Runs a 4-phase pipeline: five expert lenses (Practitioner, Academic, Skeptic, Economist, Historian) -> contradiction map -> synthesized HTML report -> adversarial peer review + primary-source verification. Best for topics where multiple viewpoints and fact-checked claims matter; overkill for a simple factual lookup.","https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fstorm-research\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7A8FKABSH98BQ9SNWW3V925","research","Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.","https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M7A8F2PQMKSXWPNKX89C62T3","last30days","Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.","https:\u002F\u002Fgithub.com\u002FRabot-Dutilleul\u002FFabien-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flast30days\u002FSKILL.md",[],[]]