[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADC44957SVQF96R5YY247P":3,"skill-same:01M6ADC44957SVQF96R5YY247P":98},{"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":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6ADC44957SVQF96R5YY247P","versioning-policy",null,"Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","github\u002Fgh-aw","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3VCZ4WKQSFSRTPN7N9DN",5633,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"policy","versioning policy","versioning","for","cli","incidents","resolution","incident","gate","implementation","version","Rules","workspace","ci","npm","semver","release","squad","pr","sdk","2026-11-10 10:12:30",false,"---\r\nname: \"versioning-policy\"\r\ndescription: \"Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents\"\r\ndomain: \"release, versioning, npm, CI\"\r\nconfidence: \"medium\"\r\nsource: \"earned (PR #640 workspace resolution incident, PR #116 prerelease leak, CI gate implementation)\"\r\n---\r\n\r\n## Context\r\n\r\nSquad is a monorepo with two publishable npm packages (`@bradygaster\u002Fsquad-sdk` and `@bradygaster\u002Fsquad-cli`) managed via npm workspaces. Version mismatches and prerelease leaks have caused production incidents — most notably PR #640, where a `-build.N` prerelease version silently broke workspace dependency resolution.\r\n\r\nThis skill codifies the versioning rules every agent must follow.\r\n\r\n## 1. Version Format\r\n\r\nAll packages use **strict semver**: `MAJOR.MINOR.PATCH`\r\n\r\n- ✅ `0.9.1`, `1.0.0`, `0.10.0`\r\n- ❌ `0.9.1-build.4`, `0.9.1-preview.1`, `0.8.6.1-preview`\r\n\r\nNo prerelease suffixes on `dev` or `main` branches — ever.\r\n\r\n## 2. Prerelease Versions Are Ephemeral\r\n\r\nThe `scripts\u002Fbump-build.mjs` script creates `-build.N` versions (e.g., `0.9.1-build.4`) for **local development testing only**.\r\n\r\nRules:\r\n- `-build.N` versions are created automatically during local `npm run build`\r\n- They are **never committed** to `dev` or `main`\r\n- The script skips itself in CI (`CI=true` or `SKIP_BUILD_BUMP=1`)\r\n- If you see a `-build.N` version in a PR diff, it is a bug — reject the PR\r\n\r\n## 3. SDK and CLI Version Sync\r\n\r\nBoth `@bradygaster\u002Fsquad-sdk` and `@bradygaster\u002Fsquad-cli` **MUST have the same version** at all times. The root `package.json` version must also match.\r\n\r\n`bump-build.mjs` enforces this by updating all three `package.json` files in lockstep (root + `packages\u002Fsquad-sdk` + `packages\u002Fsquad-cli`).\r\n\r\nIf versions diverge, workspace resolution silently breaks (see §4).\r\n\r\n## 4. npm Workspace Semver Footgun\r\n\r\nThe CLI depends on the SDK via a workspace dependency with a semver range:\r\n\r\n```json\r\n\"@bradygaster\u002Fsquad-sdk\": \">=0.9.0\"\r\n```\r\n\r\n**Critical:** Per the semver specification, `>=0.9.0` does **NOT** match `0.9.1-build.4`.\r\n\r\nSemver prerelease versions (anything with a `-` suffix) are only matched by ranges that explicitly reference the same `MAJOR.MINOR.PATCH` base with a prerelease comparator. A bare `>=0.9.0` range skips all prerelease versions.\r\n\r\n**What happens:** When the local SDK has version `0.9.1-build.4`, npm's workspace resolution fails to match the `>=0.9.0` range. npm then **silently installs a stale published version** from the npm registry instead of using the local workspace link. The build succeeds but runs against old SDK code.\r\n\r\nThis is the root cause of the **PR #640 incident**, where workspace packages appeared linked but were actually running against stale registry versions.\r\n\r\n## 5. Who Bumps Versions\r\n\r\n**Surgeon (Release Manager) owns all version bumps.**\r\n\r\n| Agent | May modify `version` in package.json? |\r\n|-------|---------------------------------------|\r\n| Surgeon | ✅ Yes — sole owner of version bumps |\r\n| Any other agent | ❌ No — unless explicitly fixing a prerelease leak |\r\n\r\nIf you discover a prerelease version committed to `dev` or `main`, you may fix it (revert to the clean release version) without Surgeon's approval. This is a safety escape hatch, not a license to manage versions.\r\n\r\n## 6. Version Bump Lifecycle\r\n\r\n```\r\n┌─────────────────────────────────────────────────────────┐\r\n│  Development phase                                      │\r\n│  Versions stay at current release: 0.9.1                │\r\n│  bump-build.mjs creates -build.N locally (not committed)│\r\n├─────────────────────────────────────────────────────────┤\r\n│  Pre-release testing                                    │\r\n│  bump-build.mjs → 0.9.1-build.1, -build.2, ...         │\r\n│  Local only. Never committed. Never pushed.             │\r\n├─────────────────────────────────────────────────────────┤\r\n│  Release                                                │\r\n│  Surgeon bumps to next version (e.g., 0.9.2 or 0.10.0) │\r\n│  Tags, publishes to npm registry                        │\r\n├─────────────────────────────────────────────────────────┤\r\n│  Post-release                                           │\r\n│  Versions stay at the new release version (e.g., 0.9.2) │\r\n│  Development continues on clean version                 │\r\n└─────────────────────────────────────────────────────────┘\r\n```\r\n\r\n## 7. CI Enforcement\r\n\r\nThe **`prerelease-version-guard`** CI gate blocks any PR to `dev` or `main` that contains prerelease version strings in `package.json` files.\r\n\r\n- The gate scans all three `package.json` files for `-` in the version field\r\n- PRs with prerelease versions **cannot merge** until the version is cleaned\r\n- The `skip-version-check` label bypasses the gate — use **only** for the bump-build script's own PR (if applicable), and only with Surgeon's approval\r\n\r\n## 8. Incident Reference — PR #640\r\n\r\n**PR #640** is the cautionary tale for this entire policy.\r\n\r\n**What happened:** Prerelease versions (`0.9.1-build.4`) were committed to a branch. The workspace dependency `>=0.9.0` failed to match the prerelease version per semver spec. npm silently installed a stale published SDK from the registry instead of linking the local workspace copy. Four PRs (#637–#640) attempted iterative patches before the root cause was identified.\r\n\r\n**Root cause:** No versioning policy existed. Agents didn't know that prerelease versions break workspace resolution, or that only Surgeon should modify versions.\r\n\r\n**Resolution:** This skill, the `prerelease-version-guard` CI gate, and the team decision to centralize version ownership under Surgeon.\r\n\r\n## Quick Reference\r\n\r\n| Rule | Summary |\r\n|------|---------|\r\n| Format | `MAJOR.MINOR.PATCH` — no prerelease on dev\u002Fmain |\r\n| Prerelease | `-build.N` is local-only, never committed |\r\n| Sync | SDK + CLI + root must have identical versions |\r\n| Ownership | Surgeon bumps versions; others don't touch them |\r\n| CI gate | `prerelease-version-guard` blocks prerelease PRs |\r\n| Escape hatch | Any agent may revert a prerelease leak to clean version |\r\n| Footgun | `>=0.9.0` does NOT match `0.9.1-build.4` per semver |\r\n","## Context\r\n\r\nSquad is a monorepo with two publishable npm packages (`@bradygaster\u002Fsquad-sdk` and `@bradygaster\u002Fsquad-cli`) managed via npm workspaces. Version mismatches and prerelease leaks have caused production incidents — most notably PR #640, where a `-build.N` prerelease version silently broke workspace dependency resolution.\r\n\r\nThis skill codifies the versioning rules every agent must follow.\r\n\r\n## 1. Version Format\r\n\r\nAll packages use **strict semver**: `MAJOR.MINOR.PATCH`\r\n\r\n- ✅ `0.9.1`, `1.0.0`, `0.10.0`\r\n- ❌ `0.9.1-build.4`, `0.9.1-preview.1`, `0.8.6.1-preview`\r\n\r\nNo prerelease suffixes on `dev` or `main` branches — ever.\r\n\r\n## 2. Prerelease Versions Are Ephemeral\r\n\r\nThe `scripts\u002Fbump-build.mjs` script creates `-build.N` versions (e.g., `0.9.1-build.4`) for **local development testing only**.\r\n\r\nRules:\r\n- `-build.N` versions are created automatically during local `npm run build`\r\n- They are **never committed** to `dev` or `main`\r\n- The script skips itself in CI (`CI=true` or `SKIP_BUILD_BUMP=1`)\r\n- If you see a `-build.N` version in a PR diff, it is a bug — reject the PR\r\n\r\n## 3. SDK and CLI Version Sync\r\n\r\nBoth `@bradygaster\u002Fsquad-sdk` and `@bradygaster\u002Fsquad-cli` **MUST have the same version** at all times. The root `package.json` version must also match.\r\n\r\n`bump-build.mjs` enforces this by updating all three `package.json` files in lockstep (root + `packages\u002Fsquad-sdk` + `packages\u002Fsquad-cli`).\r\n\r\nIf versions diverge, workspace resolution silently breaks (see §4).\r\n\r\n## 4. npm Workspace Semver Footgun\r\n\r\nThe CLI depends on the SDK via a workspace dependency with a semver range:\r\n\r\n```json\r\n\"@bradygaster\u002Fsquad-sdk\": \">=0.9.0\"\r\n```\r\n\r\n**Critical:** Per the semver specification, `>=0.9.0` does **NOT** match `0.9.1-build.4`.\r\n\r\nSemver prerelease versions (anything with a `-` suffix) are only matched by ranges that explicitly reference the same `MAJOR.MINOR.PATCH` base with a prerelease comparator. A bare `>=0.9.0` range skips all prerelease versions.\r\n\r\n**What happens:** When the local SDK has version `0.9.1-build.4`, npm's workspace resolution fails to match the `>=0.9.0` range. npm then **silently installs a stale published version** from the npm registry instead of using the local workspace link. The build succeeds but runs against old SDK code.\r\n\r\nThis is the root cause of the **PR #640 incident**, where workspace packages appeared linked but were actually running against stale registry versions.\r\n\r\n## 5. Who Bumps Versions\r\n\r\n**Surgeon (Release Manager) owns all version bumps.**\r\n\r\n| Agent | May modify `version` in package.json? |\r\n|-------|---------------------------------------|\r\n| Surgeon | ✅ Yes — sole owner of version bumps |\r\n| Any other agent | ❌ No — unless explicitly fixing a prerelease leak |\r\n\r\nIf you discover a prerelease version committed to `dev` or `main`, you may fix it (revert to the clean release version) without Surgeon's approval. This is a safety escape hatch, not a license to manage versions.\r\n\r\n## 6. Version Bump Lifecycle\r\n\r\n```\r\n┌─────────────────────────────────────────────────────────┐\r\n│  Development phase                                      │\r\n│  Versions stay at current release: 0.9.1                │\r\n│  bump-build.mjs creates -build.N locally (not committed)│\r\n├─────────────────────────────────────────────────────────┤\r\n│  Pre-release testing                                    │\r\n│  bump-build.mjs → 0.9.1-build.1, -build.2, ...         │\r\n│  Local only. Never committed. Never pushed.             │\r\n├─────────────────────────────────────────────────────────┤\r\n│  Release                                                │\r\n│  Surgeon bumps to next version (e.g., 0.9.2 or 0.10.0) │\r\n│  Tags, publishes to npm registry                        │\r\n├─────────────────────────────────────────────────────────┤\r\n│  Post-release                                           │\r\n│  Versions stay at the new release version (e.g., 0.9.2) │\r\n│  Development continues on clean version                 │\r\n└─────────────────────────────────────────────────────────┘\r\n```\r\n\r\n## 7. CI Enforcement\r\n\r\nThe **`prerelease-version-guard`** CI gate blocks any PR to `dev` or `main` that contains prerelease version strings in `package.json` files.\r\n\r\n- The gate scans all three `package.json` files for `-` in the version field\r\n- PRs with prerelease versions **cannot merge** until the version is cleaned\r\n- The `skip-version-check` label bypasses the gate — use **only** for the bump-build script's own PR (if applicable), and only with Surgeon's approval\r\n\r\n## 8. Incident Reference — PR #640\r\n\r\n**PR #640** is the cautionary tale for this entire policy.\r\n\r\n**What happened:** Prerelease versions (`0.9.1-build.4`) were committed to a branch. The workspace dependency `>=0.9.0` failed to match the prerelease version per semver spec. npm silently installed a stale published SDK from the registry instead of linking the local workspace copy. Four PRs (#637–#640) attempted iterative patches before the root cause was identified.\r\n\r\n**Root cause:** No versioning policy existed. Agents didn't know that prerelease versions break workspace resolution, or that only Surgeon should modify versions.\r\n\r\n**Resolution:** This skill, the `prerelease-version-guard` CI gate, and the team decision to centralize version ownership under Surgeon.\r\n\r\n## Quick Reference\r\n\r\n| Rule | Summary |\r\n|------|---------|\r\n| Format | `MAJOR.MINOR.PATCH` — no prerelease on dev\u002Fmain |\r\n| Prerelease | `-build.N` is local-only, never committed |\r\n| Sync | SDK + CLI + root must have identical versions |\r\n| Ownership | Surgeon bumps versions; others don't touch them |\r\n| CI gate | `prerelease-version-guard` blocks prerelease PRs |\r\n| Escape hatch | Any agent may revert a prerelease leak to clean version |\r\n| Footgun | `>=0.9.0` does NOT match `0.9.1-build.4` per semver |\r\n",{"name":5,"domain":44,"source":45,"confidence":46,"description":7},"release, versioning, npm, CI","earned (PR #640 workspace resolution incident, PR #116 prerelease leak, CI gate implementation)","medium","main","8541229759617347888641eba917d3b0ad66a984",".squad\u002Ftemplates\u002Fskills\u002Fversioning-policy",626,"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-14 06:33:26",{"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 versioning-policy",{"tool":63,"command":64},"bunx","bunx skills add github\u002Fgh-aw --skill versioning-policy",{"tool":66,"command":67},"pnpm","pnpm dlx skills add github\u002Fgh-aw --skill versioning-policy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",true,[71,77,80,84,90,94],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fcomputer_vision_architectures.md","REFERENCE","参考文档",1447,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-computer-vision\u002Freferences\u002Fcomputer_vision_architectures.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":79},"references\u002Fobject_detection_optimization.md","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-computer-vision\u002Freferences\u002Fobject_detection_optimization.md",{"path":81,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fproduction_vision_systems.md",1439,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-computer-vision\u002Freferences\u002Fproduction_vision_systems.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fdataset_pipeline_builder.py","SCRIPT","脚本",2817,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-computer-vision\u002Fscripts\u002Fdataset_pipeline_builder.py",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Finference_optimizer.py",2794,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-computer-vision\u002Fscripts\u002Finference_optimizer.py",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fvision_model_trainer.py",2797,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-computer-vision\u002Fscripts\u002Fvision_model_trainer.py",[99,126,144,170,188,213],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":113,"publishedAt":39},"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",[105,110],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":111,"categoryName":112,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000023","Skill与智能体开发",[9,114,115,116,117,118,22,119,120,121,122,123,124,125,23],"agentic","workflows","agentic workflows","github agentic workflows","writing","github cli","extension","gh","markdown","github actions","actions","compiling",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":39},"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",[],[133,134,135,136,137,138,139,140,141,142,143],"compatibility","windows compatibility","windows","patterns","bugs","path","high","platform","cross-platform","command","git",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":154,"publishedAt":39},"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",[150,153],{"categoryNo":151,"categoryName":152,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":111,"categoryName":112,"taxonomyType":108,"taxonomyTypeDesc":109},[155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,22],"tiered memory","memory","cold","runtime","three","proposal","memory-management","spawn","management","context","model","wiki","agent memory","performance","design",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":39},"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",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000008","测试与质量",[180,181,182,183,184,185,26,186,187,139],"test","test discipline","discipline","when","quality","tests","update","sync",{"skillNo":189,"name":36,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":39},"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",[],[36,194,195,196,197,198,23,199,200,201,202,203,204,205,206,207,208,209,210,211,142,165,212],"plugins","issues","state","squad commands","sessions","show me","upgrade","interactive menu","invoke","coordinator","as","commands","options","me","natural language","do","show","install","team",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":39},"01M6ADBTRD3ZCJ9A96P5JEGQD2","squad-version-check","Internals of how @bradygaster\u002Fsquad-cli stamps its version, how `squad upgrade` works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fsquad-version-check\u002FSKILL.md",[],[29,220,36,221,222,223,22,224,203,225,226,200,227,228,229,230,33,231,9,23],"check","squad version check","it","2026","latest","recon","how to","probe","prompt","how","data","registry"]