[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AW6DY4CERTYVCWKMHNYVDC":3,"skill-same:01M7AW6DY4CERTYVCWKMHNYVDC":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AW6DY4CERTYVCWKMHNYVDC","yun-spawn-worktree",null,"Spawn an isolated git worktree for a synced repo so parallel work never collides. Use when the user wants to parallelize, work a task in isolation, or run one of several tickets on its own branch — or when another skill (e.g. yun-implement) needs an isolated worktree to build in. Creates .worktrees\u002F\u003Crepo>\u002F\u003Ctask>\u002F on its own branch.","matiinchauspe\u002Fyunque","matiinchauspe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7861346?v=4","01M7AW106HSV1DVWJSQQBD6BYB","Matias","01M7AW107JZVCTQHZEED16N5PZ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-spawn-worktree\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: yun-spawn-worktree\ndescription: Spawn an isolated git worktree for a synced repo so parallel work never collides. Use when the user wants to parallelize, work a task in isolation, or run one of several tickets on its own branch — or when another skill (e.g. yun-implement) needs an isolated worktree to build in. Creates .worktrees\u002F\u003Crepo>\u002F\u003Ctask>\u002F on its own branch.\n---\n\n# yun-spawn-worktree\n\nSpawn an ephemeral **worktree** — a second working tree of a synced repo, on its own branch,\nso parallel agents each get an isolated tree and branch instead of editing or scanning each\nother's. It only creates the worktree; removing it is the caller's job once the work lands\n(`git worktree remove`, or the `\u002Fyun-clean-worktree` sweep). This is the light isolation rung —\npure git, local, no sandbox — the seam a heavier execution substrate plugs in above.\n\n## Preconditions\n\n- You MUST be at the workspace root (the dir with `AGENTS.md` and `skills\u002F`). Stay there —\n  operate with `git -C`, never `cd` into the repo or the worktree (AGENTS.md rule 1).\n- `repos\u002F\u003Crepo>\u002F` exists and is a FULL clone — worktrees need full history, so a shallow\n  clone won't do (`yun-sync-repo` clones full by default).\n\n## Inputs\n\n- `\u003Crepo>` — the synced repo under `repos\u002F\u003Crepo>\u002F`.\n- `\u003Ctask>` — a kebab-case slug for the work; names both the worktree dir and its branch. It may\n  carry slash-separated segments (`\u003Cprefix>\u002F\u003Cticket>-\u003Cnonce>`) so a caller spawning a whole set\n  can group them under one branch namespace it can list and prune later; git takes the slashes in\n  a branch name, and the worktree simply nests to match.\n- `\u003Cbase>` — the ref to branch from. A base the user or caller names is the base. Absent one,\n  it is the repo's **mainline**, resolved by the rule in `skills\u002F_shared\u002Fexecution-convention.md`\n  (a live `develop`, else `main` or `master`, never `origin\u002FHEAD`); none of them → STOP and ask\n  for a base.\n\n## Steps\n\n1. **Resolve and check for collision.** Confirm `repos\u002F\u003Crepo>\u002F` is a repo. If\n   `.worktrees\u002F\u003Crepo>\u002F\u003Ctask>\u002F` already exists, or a branch named `\u003Ctask>` already exists in\n   the repo, STOP and ask — never clobber another agent's worktree or branch. Done when the\n   target path and branch name are both free.\n\n2. **Spawn the worktree on a new branch.** Add it at an ABSOLUTE path — a path passed to\n   `git -C` is read against the repo dir, not the workspace root, so an absolute path is what\n   keeps the worktree under `.worktrees\u002F` (outside the repo's own tree, per rule 3):\n   ```\n   git -C repos\u002F\u003Crepo> worktree add -b \u003Ctask> \"$(pwd)\u002F.worktrees\u002F\u003Crepo>\u002F\u003Ctask>\" \u003Cbase>\n   ```\n   Done when the command succeeds.\n\n3. **Verify isolation.** `git -C repos\u002F\u003Crepo> worktree list` shows the new worktree on branch\n   `\u003Ctask>`. `git status` at the workspace root does NOT list it — `.worktrees\u002F` is gitignored;\n   if it appears, the workspace `.gitignore` is broken, so fix it before continuing. Done when\n   both hold.\n\n4. **Report.** Give the ready path `.worktrees\u002F\u003Crepo>\u002F\u003Ctask>\u002F`, its branch, and the base it was\n   cut from. When the base was the mainline and `repos\u002F\u003Crepo>` has another branch checked out,\n   name that branch too (\"`repos\u002F\u003Crepo>` is on `\u003Cbranch>`; cut from `\u003Cmainline>`\"), so a human who\n   meant to stack on it sees it now. Work runs there\n   via `git -C .worktrees\u002F\u003Crepo>\u002F\u003Ctask>`, from the workspace root. Done when the caller has the\n   path and branch.\n\n## Cleanup\n\nThe caller's job once the work lands, not this skill's: `git -C repos\u002F\u003Crepo> worktree remove\n.worktrees\u002F\u003Crepo>\u002F\u003Ctask>`, or the `\u002Fyun-clean-worktree` sweep for every worktree whose work has\nmerged. Run `git worktree prune` BEFORE deleting a source repo, and\n`git worktree repair` if the workspace moves (AGENTS.md rule 4).\n","# yun-spawn-worktree\n\nSpawn an ephemeral **worktree** — a second working tree of a synced repo, on its own branch,\nso parallel agents each get an isolated tree and branch instead of editing or scanning each\nother's. It only creates the worktree; removing it is the caller's job once the work lands\n(`git worktree remove`, or the `\u002Fyun-clean-worktree` sweep). This is the light isolation rung —\npure git, local, no sandbox — the seam a heavier execution substrate plugs in above.\n\n## Preconditions\n\n- You MUST be at the workspace root (the dir with `AGENTS.md` and `skills\u002F`). Stay there —\n  operate with `git -C`, never `cd` into the repo or the worktree (AGENTS.md rule 1).\n- `repos\u002F\u003Crepo>\u002F` exists and is a FULL clone — worktrees need full history, so a shallow\n  clone won't do (`yun-sync-repo` clones full by default).\n\n## Inputs\n\n- `\u003Crepo>` — the synced repo under `repos\u002F\u003Crepo>\u002F`.\n- `\u003Ctask>` — a kebab-case slug for the work; names both the worktree dir and its branch. It may\n  carry slash-separated segments (`\u003Cprefix>\u002F\u003Cticket>-\u003Cnonce>`) so a caller spawning a whole set\n  can group them under one branch namespace it can list and prune later; git takes the slashes in\n  a branch name, and the worktree simply nests to match.\n- `\u003Cbase>` — the ref to branch from. A base the user or caller names is the base. Absent one,\n  it is the repo's **mainline**, resolved by the rule in `skills\u002F_shared\u002Fexecution-convention.md`\n  (a live `develop`, else `main` or `master`, never `origin\u002FHEAD`); none of them → STOP and ask\n  for a base.\n\n## Steps\n\n1. **Resolve and check for collision.** Confirm `repos\u002F\u003Crepo>\u002F` is a repo. If\n   `.worktrees\u002F\u003Crepo>\u002F\u003Ctask>\u002F` already exists, or a branch named `\u003Ctask>` already exists in\n   the repo, STOP and ask — never clobber another agent's worktree or branch. Done when the\n   target path and branch name are both free.\n\n2. **Spawn the worktree on a new branch.** Add it at an ABSOLUTE path — a path passed to\n   `git -C` is read against the repo dir, not the workspace root, so an absolute path is what\n   keeps the worktree under `.worktrees\u002F` (outside the repo's own tree, per rule 3):\n   ```\n   git -C repos\u002F\u003Crepo> worktree add -b \u003Ctask> \"$(pwd)\u002F.worktrees\u002F\u003Crepo>\u002F\u003Ctask>\" \u003Cbase>\n   ```\n   Done when the command succeeds.\n\n3. **Verify isolation.** `git -C repos\u002F\u003Crepo> worktree list` shows the new worktree on branch\n   `\u003Ctask>`. `git status` at the workspace root does NOT list it — `.worktrees\u002F` is gitignored;\n   if it appears, the workspace `.gitignore` is broken, so fix it before continuing. Done when\n   both hold.\n\n4. **Report.** Give the ready path `.worktrees\u002F\u003Crepo>\u002F\u003Ctask>\u002F`, its branch, and the base it was\n   cut from. When the base was the mainline and `repos\u002F\u003Crepo>` has another branch checked out,\n   name that branch too (\"`repos\u002F\u003Crepo>` is on `\u003Cbranch>`; cut from `\u003Cmainline>`\"), so a human who\n   meant to stack on it sees it now. Work runs there\n   via `git -C .worktrees\u002F\u003Crepo>\u002F\u003Ctask>`, from the workspace root. Done when the caller has the\n   path and branch.\n\n## Cleanup\n\nThe caller's job once the work lands, not this skill's: `git -C repos\u002F\u003Crepo> worktree remove\n.worktrees\u002F\u003Crepo>\u002F\u003Ctask>`, or the `\u002Fyun-clean-worktree` sweep for every worktree whose work has\nmerged. Run `git worktree prune` BEFORE deleting a source repo, and\n`git worktree repair` if the workspace moves (AGENTS.md rule 4).\n",{"name":5,"description":7},"main","31bfd2af63052d9bb7036b02364637ba5dc70f87","skills\u002Fyun-spawn-worktree",0,"https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe","The fools will be invencible - \r\n\r\nDevelop developing thoughts","2026-11-13 04:14:30",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add matiinchauspe\u002Fyunque --skill yun-spawn-worktree",{"tool":38,"command":39},"bunx","bunx skills add matiinchauspe\u002Fyunque --skill yun-spawn-worktree",{"tool":41,"command":42},"pnpm","pnpm dlx skills add matiinchauspe\u002Fyunque --skill yun-spawn-worktree","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-spawn-worktree\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7AW7HDMMJ372HG8PGM5RR0Z","yun-write-wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-wizard\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AW7AX7MH2S7GSG6JAD4PQY","yun-write-spec","Write the spec — consolidate a large task's settled decisions into one durable document before it is sliced into tickets. Use when the decisions are settled and the user wants them written up, or says \"write the spec\" \u002F \"escribí el spec\". Declines small fixes that need no spec.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-spec\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AW76CY32E072H8FKE8PDQ5","yun-write-pr","Write a pull request title and body that show the change — its ticket, its shape, the evidence it works, and how dangerous it is to merge.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-pr\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AW7291YQKHYGSJKGG1EVVX","yun-write-handoff","Compact the current session into a disposable handoff baton for the next agent, pointing at durable memory instead of duplicating it.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-handoff\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AW6WXBGGYX7XMWYQFMNCVJ","yun-write-agent-docs","Use when authoring or editing a document an agent reads in this workspace — a skill, a `skills\u002F_shared\u002F` contract, `AGENTS.md` or `skills\u002FREADME.md` — deciding how it is invoked, what lives in it versus a linked file, naming it, or diagnosing why a skill misfires, bloats, or fires unreliably.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-write-agent-docs\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AW6Q9K91GDDWY0YJMCYSJK","yun-tdd","Test-driven development — the red → green loop, tests written only at pre-agreed seams. Use when the user wants to build a feature or fix a bug test-first, or mentions TDD or red-green. Reached by the implement flow to drive a build at a seam.","https:\u002F\u002Fgithub.com\u002Fmatiinchauspe\u002Fyunque\u002Fblob\u002Fmain\u002Fskills\u002Fyun-tdd\u002FSKILL.md",[],[]]