[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADA4NBXYMYEM0BGFJ5MTMP":3,"skill-same:01M6ADA4NBXYMYEM0BGFJ5MTMP":85},{"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":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6ADA4NBXYMYEM0BGFJ5MTMP","git-workflow",null,"Squad branching model: dev-first workflow with insiders preview channel","github\u002Fgh-aw","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3VCZ4WKQSFSRTPN7N9DN",5621,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fgit-workflow\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"git workflow","workflow","git","high","with","branching","control","preview","version-control","version","channel","decision","model","team","first","dev","squad","2026-11-10 10:12:30",false,"---\nname: \"git-workflow\"\ndescription: \"Squad branching model: dev-first workflow with insiders preview channel\"\ndomain: \"version-control\"\nconfidence: \"high\"\nsource: \"team-decision\"\n---\n\n## Context\n\nSquad uses a three-branch model. **All feature work starts from `dev`, not `main`.**\n\n| Branch | Purpose | Publishes |\n|--------|---------|-----------|\n| `main` | Released, tagged, in-npm code only | `npm publish` on tag |\n| `dev` | Integration branch — all feature work lands here | `npm publish --tag preview` on merge |\n| `insiders` | Early-access channel — synced from dev | `npm publish --tag insiders` on sync |\n\n## Branch Naming Convention\n\nIssue branches MUST use: `squad\u002F{issue-number}-{kebab-case-slug}`\n\nExamples:\n- `squad\u002F195-fix-version-stamp-bug`\n- `squad\u002F42-add-profile-api`\n\n## Workflow for Issue Work\n\n1. **Branch from dev:**\n   ```bash\n   git checkout dev\n   git pull origin dev\n   git checkout -b squad\u002F{issue-number}-{slug}\n   ```\n\n2. **Mark issue in-progress:**\n   ```bash\n   gh issue edit {number} --add-label \"status:in-progress\"\n   ```\n\n3. **Create draft PR targeting dev:**\n   ```bash\n   gh pr create --base dev --title \"{description}\" --body \"Closes #{issue-number}\" --draft\n   ```\n\n4. **Do the work.** Make changes, write tests, commit with issue reference.\n\n5. **Push and mark ready:**\n   ```bash\n   git push -u origin squad\u002F{issue-number}-{slug}\n   gh pr ready\n   ```\n\n6. **After merge to dev:**\n   ```bash\n   git checkout dev\n   git pull origin dev\n   git branch -d squad\u002F{issue-number}-{slug}\n   git push origin --delete squad\u002F{issue-number}-{slug}\n   ```\n\n## Parallel Multi-Issue Work (Worktrees)\n\nWhen the coordinator routes multiple issues simultaneously (e.g., \"fix bugs X, Y, and Z\"), use `git worktree` to give each agent an isolated working directory. No filesystem collisions, no branch-switching overhead.\n\n### When to Use Worktrees vs Sequential\n\n| Scenario | Strategy |\n|----------|----------|\n| Single issue | Standard workflow above — no worktree needed |\n| 2+ simultaneous issues in same repo | Worktrees — one per issue |\n| Work spanning multiple repos | Separate clones as siblings (see Multi-Repo below) |\n\n### Setup\n\nFrom the main clone (must be on dev or any branch):\n\n```bash\n# Ensure dev is current\ngit fetch origin dev\n\n# Create a worktree per issue — siblings to the main clone\ngit worktree add ..\u002Fsquad-195 -b squad\u002F195-fix-stamp-bug origin\u002Fdev\ngit worktree add ..\u002Fsquad-193 -b squad\u002F193-refactor-loader origin\u002Fdev\n```\n\n**Naming convention:** `..\u002F{repo-name}-{issue-number}` (e.g., `..\u002Fsquad-195`, `..\u002Fsquad-pr-42`).\n\nEach worktree:\n- Has its own working directory and index\n- Is on its own `squad\u002F{issue-number}-{slug}` branch from dev\n- Shares the same `.git` object store (disk-efficient)\n\n### Per-Worktree Agent Workflow\n\nEach agent operates inside its worktree exactly like the single-issue workflow:\n\n```bash\ncd ..\u002Fsquad-195\n\n# Work normally — commits, tests, pushes\ngit add -A && git commit -m \"fix: stamp bug (#195)\"\ngit push -u origin squad\u002F195-fix-stamp-bug\n\n# Create PR targeting dev\ngh pr create --base dev --title \"fix: stamp bug\" --body \"Closes #195\" --draft\n```\n\nAll PRs target `dev` independently. Agents never interfere with each other's filesystem.\n\n### .squad\u002F State in Worktrees\n\nThe `.squad\u002F` directory exists in each worktree as a copy. This is safe because:\n- `.gitattributes` declares `merge=union` on append-only files (history.md, decisions.md, logs)\n- Each agent appends to its own section; union merge reconciles on PR merge to dev\n- **Rule:** Never rewrite or reorder `.squad\u002F` files in a worktree — append only\n\n### Cleanup After Merge\n\nAfter a worktree's PR is merged to dev:\n\n```bash\n# From the main clone\ngit worktree remove ..\u002Fsquad-195\ngit worktree prune          # clean stale metadata\ngit branch -d squad\u002F195-fix-stamp-bug\ngit push origin --delete squad\u002F195-fix-stamp-bug\n```\n\nIf a worktree was deleted manually (rm -rf), `git worktree prune` recovers the state.\n\n---\n\n## Multi-Repo Downstream Scenarios\n\nWhen work spans multiple repositories (e.g., squad-cli changes need squad-sdk changes, or a user's app depends on squad):\n\n### Setup\n\nClone downstream repos as siblings to the main repo:\n\n```\n~\u002Fwork\u002F\n  squad-pr\u002F          # main repo\n  squad-sdk\u002F         # downstream dependency\n  user-app\u002F          # consumer project\n```\n\nEach repo gets its own issue branch following its own naming convention. If the downstream repo also uses Squad conventions, use `squad\u002F{issue-number}-{slug}`.\n\n### Coordinated PRs\n\n- Create PRs in each repo independently\n- Link them in PR descriptions:\n  ```\n  Closes #42\n\n  **Depends on:** squad-sdk PR #17 (squad-sdk changes required for this feature)\n  ```\n- Merge order: dependencies first (e.g., squad-sdk), then dependents (e.g., squad-cli)\n\n### Local Linking for Testing\n\nBefore pushing, verify cross-repo changes work together:\n\n```bash\n# Node.js \u002F npm\ncd ..\u002Fsquad-sdk && npm link\ncd ..\u002Fsquad-pr && npm link squad-sdk\n\n# Go\n# Use replace directive in go.mod:\n# replace github.com\u002Forg\u002Fsquad-sdk => ..\u002Fsquad-sdk\n\n# Python\ncd ..\u002Fsquad-sdk && pip install -e .\n```\n\n**Important:** Remove local links before committing. `npm link` and `go replace` are dev-only — CI must use published packages or PR-specific refs.\n\n### Worktrees + Multi-Repo\n\nThese compose naturally. You can have:\n- Multiple worktrees in the main repo (parallel issues)\n- Separate clones for downstream repos\n- Each combination operates independently\n\n---\n\n## Anti-Patterns\n\n- ❌ Branching from main (branch from dev)\n- ❌ PR targeting main directly (target dev)\n- ❌ Non-conforming branch names (must be squad\u002F{number}-{slug})\n- ❌ Committing directly to main or dev (use PRs)\n- ❌ Switching branches in the main clone while worktrees are active (use worktrees instead)\n- ❌ Using worktrees for cross-repo work (use separate clones)\n- ❌ Leaving stale worktrees after PR merge (clean up immediately)\n\n## Promotion Pipeline\n\n- dev → insiders: Automated sync on green build\n- dev → main: Manual merge when ready for stable release, then tag\n- Hotfixes: Branch from main as `hotfix\u002F{slug}`, PR to dev, cherry-pick to main if urgent\n","## Context\n\nSquad uses a three-branch model. **All feature work starts from `dev`, not `main`.**\n\n| Branch | Purpose | Publishes |\n|--------|---------|-----------|\n| `main` | Released, tagged, in-npm code only | `npm publish` on tag |\n| `dev` | Integration branch — all feature work lands here | `npm publish --tag preview` on merge |\n| `insiders` | Early-access channel — synced from dev | `npm publish --tag insiders` on sync |\n\n## Branch Naming Convention\n\nIssue branches MUST use: `squad\u002F{issue-number}-{kebab-case-slug}`\n\nExamples:\n- `squad\u002F195-fix-version-stamp-bug`\n- `squad\u002F42-add-profile-api`\n\n## Workflow for Issue Work\n\n1. **Branch from dev:**\n   ```bash\n   git checkout dev\n   git pull origin dev\n   git checkout -b squad\u002F{issue-number}-{slug}\n   ```\n\n2. **Mark issue in-progress:**\n   ```bash\n   gh issue edit {number} --add-label \"status:in-progress\"\n   ```\n\n3. **Create draft PR targeting dev:**\n   ```bash\n   gh pr create --base dev --title \"{description}\" --body \"Closes #{issue-number}\" --draft\n   ```\n\n4. **Do the work.** Make changes, write tests, commit with issue reference.\n\n5. **Push and mark ready:**\n   ```bash\n   git push -u origin squad\u002F{issue-number}-{slug}\n   gh pr ready\n   ```\n\n6. **After merge to dev:**\n   ```bash\n   git checkout dev\n   git pull origin dev\n   git branch -d squad\u002F{issue-number}-{slug}\n   git push origin --delete squad\u002F{issue-number}-{slug}\n   ```\n\n## Parallel Multi-Issue Work (Worktrees)\n\nWhen the coordinator routes multiple issues simultaneously (e.g., \"fix bugs X, Y, and Z\"), use `git worktree` to give each agent an isolated working directory. No filesystem collisions, no branch-switching overhead.\n\n### When to Use Worktrees vs Sequential\n\n| Scenario | Strategy |\n|----------|----------|\n| Single issue | Standard workflow above — no worktree needed |\n| 2+ simultaneous issues in same repo | Worktrees — one per issue |\n| Work spanning multiple repos | Separate clones as siblings (see Multi-Repo below) |\n\n### Setup\n\nFrom the main clone (must be on dev or any branch):\n\n```bash\n# Ensure dev is current\ngit fetch origin dev\n\n# Create a worktree per issue — siblings to the main clone\ngit worktree add ..\u002Fsquad-195 -b squad\u002F195-fix-stamp-bug origin\u002Fdev\ngit worktree add ..\u002Fsquad-193 -b squad\u002F193-refactor-loader origin\u002Fdev\n```\n\n**Naming convention:** `..\u002F{repo-name}-{issue-number}` (e.g., `..\u002Fsquad-195`, `..\u002Fsquad-pr-42`).\n\nEach worktree:\n- Has its own working directory and index\n- Is on its own `squad\u002F{issue-number}-{slug}` branch from dev\n- Shares the same `.git` object store (disk-efficient)\n\n### Per-Worktree Agent Workflow\n\nEach agent operates inside its worktree exactly like the single-issue workflow:\n\n```bash\ncd ..\u002Fsquad-195\n\n# Work normally — commits, tests, pushes\ngit add -A && git commit -m \"fix: stamp bug (#195)\"\ngit push -u origin squad\u002F195-fix-stamp-bug\n\n# Create PR targeting dev\ngh pr create --base dev --title \"fix: stamp bug\" --body \"Closes #195\" --draft\n```\n\nAll PRs target `dev` independently. Agents never interfere with each other's filesystem.\n\n### .squad\u002F State in Worktrees\n\nThe `.squad\u002F` directory exists in each worktree as a copy. This is safe because:\n- `.gitattributes` declares `merge=union` on append-only files (history.md, decisions.md, logs)\n- Each agent appends to its own section; union merge reconciles on PR merge to dev\n- **Rule:** Never rewrite or reorder `.squad\u002F` files in a worktree — append only\n\n### Cleanup After Merge\n\nAfter a worktree's PR is merged to dev:\n\n```bash\n# From the main clone\ngit worktree remove ..\u002Fsquad-195\ngit worktree prune          # clean stale metadata\ngit branch -d squad\u002F195-fix-stamp-bug\ngit push origin --delete squad\u002F195-fix-stamp-bug\n```\n\nIf a worktree was deleted manually (rm -rf), `git worktree prune` recovers the state.\n\n---\n\n## Multi-Repo Downstream Scenarios\n\nWhen work spans multiple repositories (e.g., squad-cli changes need squad-sdk changes, or a user's app depends on squad):\n\n### Setup\n\nClone downstream repos as siblings to the main repo:\n\n```\n~\u002Fwork\u002F\n  squad-pr\u002F          # main repo\n  squad-sdk\u002F         # downstream dependency\n  user-app\u002F          # consumer project\n```\n\nEach repo gets its own issue branch following its own naming convention. If the downstream repo also uses Squad conventions, use `squad\u002F{issue-number}-{slug}`.\n\n### Coordinated PRs\n\n- Create PRs in each repo independently\n- Link them in PR descriptions:\n  ```\n  Closes #42\n\n  **Depends on:** squad-sdk PR #17 (squad-sdk changes required for this feature)\n  ```\n- Merge order: dependencies first (e.g., squad-sdk), then dependents (e.g., squad-cli)\n\n### Local Linking for Testing\n\nBefore pushing, verify cross-repo changes work together:\n\n```bash\n# Node.js \u002F npm\ncd ..\u002Fsquad-sdk && npm link\ncd ..\u002Fsquad-pr && npm link squad-sdk\n\n# Go\n# Use replace directive in go.mod:\n# replace github.com\u002Forg\u002Fsquad-sdk => ..\u002Fsquad-sdk\n\n# Python\ncd ..\u002Fsquad-sdk && pip install -e .\n```\n\n**Important:** Remove local links before committing. `npm link` and `go replace` are dev-only — CI must use published packages or PR-specific refs.\n\n### Worktrees + Multi-Repo\n\nThese compose naturally. You can have:\n- Multiple worktrees in the main repo (parallel issues)\n- Separate clones for downstream repos\n- Each combination operates independently\n\n---\n\n## Anti-Patterns\n\n- ❌ Branching from main (branch from dev)\n- ❌ PR targeting main directly (target dev)\n- ❌ Non-conforming branch names (must be squad\u002F{number}-{slug})\n- ❌ Committing directly to main or dev (use PRs)\n- ❌ Switching branches in the main clone while worktrees are active (use worktrees instead)\n- ❌ Using worktrees for cross-repo work (use separate clones)\n- ❌ Leaving stale worktrees after PR merge (clean up immediately)\n\n## Promotion Pipeline\n\n- dev → insiders: Automated sync on green build\n- dev → main: Manual merge when ready for stable release, then tag\n- Hotfixes: Branch from main as `hotfix\u002F{slug}`, PR to dev, cherry-pick to main if urgent\n",{"name":5,"domain":32,"source":46,"confidence":27,"description":7},"team-decision","main","8541229759617347888641eba917d3b0ad66a984",".squad\u002Ftemplates\u002Fskills\u002Fgit-workflow",625,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw","https:\u002F\u002Fgh.io\u002Fgh-aw","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-12 03:23:28",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add github\u002Fgh-aw --skill git-workflow",{"tool":63,"command":64},"bunx","bunx skills add github\u002Fgh-aw --skill git-workflow",{"tool":66,"command":67},"pnpm","pnpm dlx skills add github\u002Fgh-aw --skill git-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fgit-workflow\u002FSKILL.md",true,[71,77,81],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"ADR-FORMAT.md","REFERENCE","参考文档",2733,"https:\u002F\u002Fgithub.com\u002Fajrussellaudio\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.claude\u002Fskills\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"agents\u002Fopenai.yaml",101,"https:\u002F\u002Fgithub.com\u002Fajrussellaudio\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.claude\u002Fskills\u002Fdomain-modeling\u002Fagents\u002Fopenai.yaml",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"GLOSSARY-FORMAT.md",2300,"https:\u002F\u002Fgithub.com\u002Fajrussellaudio\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.claude\u002Fskills\u002Fdomain-modeling\u002FGLOSSARY-FORMAT.md",[86,111,127,150,175,193],{"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":96,"publishedAt":41},"01M6ADC942STTXHFV410J4DH0X","GitHub Agentic Workflows","GitHub Agentic Workflows (`gh-aw`) is a GitHub CLI extension for writing Agentic Workflows in markdown and compiling them to GitHub Actions.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002FSKILL.md",[92,95],{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[9,97,98,99,100,101,102,103,104,105,106,107,108,109,110],"agentic","agentic workflows","github agentic workflows","workflows","github cli","gh","extension","for","compiling","cli","writing","actions","github actions","markdown",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":41},"01M6ADC6ZXSA46N9XD6VNAP1MS","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[118,119,120,121,122,27,123,124,125,126,26],"windows","windows compatibility","compatibility","bugs","path","platform","cross-platform","patterns","command",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":41},"01M6ADC44957SVQF96R5YY247P","versioning-policy","Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[134,135,136,137,138,139,33,140,141,142,143,144,145,146,40,147,104,148,106,149],"policy","versioning policy","versioning","incident","gate","implementation","Rules","workspace","pr","ci","npm","semver","release","resolution","incidents","sdk",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":160,"publishedAt":41},"01M6ADC1PHMEAEVR87F8PDR89X","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[156,159],{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[161,162,163,36,104,164,165,166,167,168,169,170,171,172,173,174],"tiered memory","memory","memory-management","cold","proposal","runtime","three","spawn","management","context","wiki","agent memory","performance","design",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":184,"publishedAt":41},"01M6ADBZTDGFM0E25EWRQEMYEH","test-discipline","Update tests when changing APIs — no exceptions","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[181],{"categoryNo":182,"categoryName":183,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[185,186,187,188,189,27,190,137,191,192],"test discipline","discipline","test","sync","when","tests","quality","update",{"skillNo":194,"name":40,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":41},"01M6ADBX5MJP4Z7CG4XTV8ZVT8","Squad's command catalog and interactive menu. Invoke via \u002Fsquad (slash command) or natural language (\"squad commands\", \"what can squad do\", \"show me squad options\"). Presents categorized operations (Install & Upgrade, Team Management, Issues & PRs, Plugins & Skills, Model & Cost, Sessions & State) as an interactive picker. Routes to the right squad CLI command or the Squad coordinator agent.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fsquad\u002FSKILL.md",[],[40,199,200,201,202,203,204,205,206,207,208,209,210,126,36,37,211,212,213,214,215,216,106],"show","interactive menu","invoke","coordinator","as","commands","upgrade","options","me","natural language","do","install","show me","plugins","issues","state","squad commands","sessions"]