[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X1V7KYSTFQRSF2TQTATX9C":3,"skill-same:01M6X1V7KYSTFQRSF2TQTATX9C":70},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6X1V7KYSTFQRSF2TQTATX9C","versioning-policy",null,"SemVer rules for Squad's stable, preview, insider, and local package versions","github\u002Fsquad","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6X0MZ6B0WYMMDPK3Q61KER6",3391,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fpackages\u002Fsquad-sdk\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],"versioning policy","versioning","policy","workspace","for","high","insider","channels","resolution","local","incident","preview","Rules","ci","package","npm","semver","release","squad","pr","2026-11-10 10:12:30",false,"---\nname: \"versioning-policy\"\ndescription: \"SemVer rules for Squad's stable, preview, insider, and local package versions\"\ndomain: \"release, versioning, npm, CI\"\nconfidence: \"high\"\nsource: \"earned (PR #640 workspace resolution incident and automated release channels)\"\n---\n\n## Context\n\nSquad publishes `@bradygaster\u002Fsquad-sdk` and\n`@bradygaster\u002Fsquad-cli` from one npm workspace. Their versions and the root\nversion move together. A mismatched prerelease dependency can make npm silently\nresolve an older registry SDK instead of the local workspace.\n\n## 1. Supported versions\n\n| Use | Version | Committed branch |\n|---|---|---|\n| Stable release | `MAJOR.MINOR.PATCH` | `main`, and briefly `dev` during promotion |\n| Preview release | `MAJOR.MINOR.PATCH-preview.N` | `dev` |\n| Insider snapshot | `MAJOR.MINOR.PATCH-insider.N` | Generated by the insider workflow |\n| Local build | `MAJOR.MINOR.PATCH-build.N` | Never committed |\n\n`preview` is a release channel, not a branch. Stable promotion merges a\nsanitized release tree directly from `dev` to `main`.\n\n## 2. Package versions stay in lockstep\n\nThese versions must always be identical:\n\n- `package.json`\n- `packages\u002Fsquad-sdk\u002Fpackage.json`\n- `packages\u002Fsquad-cli\u002Fpackage.json`\n- the corresponding workspace entries in `package-lock.json`\n\nUse the workspace-aware version command:\n\n```bash\nnpm version \"$VERSION\" --workspaces --include-workspace-root --no-git-tag-version\n```\n\nNever edit only one package version.\n\n## 3. Prerelease workspace dependency rule\n\nThe CLI depends on the SDK through a SemVer range. SemVer deliberately excludes\nprereleases unless the comparator names a prerelease with the same base version.\nFor example, `>=0.13.0` does not match `0.14.0-preview.1`.\n\nFor every committed preview version, set both the CLI manifest and lockfile\ndependency floor to that exact preview:\n\n```bash\nnpm pkg set \"dependencies.@bradygaster\u002Fsquad-sdk=>=$VERSION\" \\\n  --workspace @bradygaster\u002Fsquad-cli\nnpm install --package-lock-only\n```\n\nFor `VERSION=0.14.0-preview.1`, the required range is\n`>=0.14.0-preview.1`. Before stable promotion, change the version and floor to\n`0.14.0` \u002F `>=0.14.0`; never leave a prerelease floor in a stable release.\n\nThis rule prevents the PR #640 failure mode, where the build succeeded against\na stale published SDK rather than the workspace SDK.\n\n## 4. Local build versions are ephemeral\n\n`scripts\u002Fbump-build.mjs` may create `-build.N` versions for local development.\n\n- Never commit a `-build.N` version.\n- The script skips itself when `CI=true` or `SKIP_BUILD_BUMP=1`.\n- If a build changes manifests locally, restore the intended release source\n  versions before committing.\n\n## 5. Release lifecycle\n\n1. On a release-preparation branch from `dev`, set the next\n   `X.Y.Z-preview.N` version and matching SDK dependency floor.\n2. Merge to `dev`, wait for CI, and dispatch `squad-release.yml` from `dev`.\n3. Repeat with a new immutable preview version when another candidate is needed.\n4. Dispatch `squad-insider-publish.yml` whenever an on-demand development\n   snapshot is needed; it computes the next immutable `X.Y.Z-insider.N`.\n5. Prepare stable `X.Y.Z` and its stable SDK dependency floor on `dev`.\n6. Dispatch `squad-promote.yml`; it sanitizes `dev`, pushes `main`, and\n   explicitly dispatches the stable release.\n7. Open the next preview-version PR for continued development.\n\nA preview such as `0.14.0-preview.1` is never renamed or converted in place.\nStable `0.14.0` is a separate immutable package version and GitHub tag.\n\n## 6. Ownership\n\nThe current Release Manager owns release version changes. Other agents may update\nversions only when explicitly assigned release work or when reverting an\naccidentally committed local `-build.N` version.\n\n## 7. CI enforcement\n\nCI verifies:\n\n- root, SDK, and CLI versions match;\n- package-lock workspace versions match;\n- committed prereleases use approved `preview` or `insider` identifiers;\n- a preview CLI dependency and lockfile entry equal `>=VERSION`;\n- stable source does not retain a prerelease dependency floor; and\n- workspace packages resolve through local links rather than stale registry\n  packages.\n\nRelease workflows repeat the dependency checks before creating a tag or\npublishing.\n\n## Quick reference\n\n| Rule | Summary |\n|---|---|\n| Insider | The workflow generates `X.Y.Z-insider.N` from the stable base version |\n| Preview | Commit `X.Y.Z-preview.N` to `dev` for an on-demand prerelease |\n| Stable | Only `X.Y.Z` may release from `main` |\n| Sync | Root, SDK, CLI, and lockfile workspace versions must match |\n| Dependency | Preview CLI range and lockfile entry must be `>=VERSION` |\n| Local build | `-build.N` is local-only and never committed |\n| Ownership | The current Release Manager owns planned release version changes |\n","## Context\n\nSquad publishes `@bradygaster\u002Fsquad-sdk` and\n`@bradygaster\u002Fsquad-cli` from one npm workspace. Their versions and the root\nversion move together. A mismatched prerelease dependency can make npm silently\nresolve an older registry SDK instead of the local workspace.\n\n## 1. Supported versions\n\n| Use | Version | Committed branch |\n|---|---|---|\n| Stable release | `MAJOR.MINOR.PATCH` | `main`, and briefly `dev` during promotion |\n| Preview release | `MAJOR.MINOR.PATCH-preview.N` | `dev` |\n| Insider snapshot | `MAJOR.MINOR.PATCH-insider.N` | Generated by the insider workflow |\n| Local build | `MAJOR.MINOR.PATCH-build.N` | Never committed |\n\n`preview` is a release channel, not a branch. Stable promotion merges a\nsanitized release tree directly from `dev` to `main`.\n\n## 2. Package versions stay in lockstep\n\nThese versions must always be identical:\n\n- `package.json`\n- `packages\u002Fsquad-sdk\u002Fpackage.json`\n- `packages\u002Fsquad-cli\u002Fpackage.json`\n- the corresponding workspace entries in `package-lock.json`\n\nUse the workspace-aware version command:\n\n```bash\nnpm version \"$VERSION\" --workspaces --include-workspace-root --no-git-tag-version\n```\n\nNever edit only one package version.\n\n## 3. Prerelease workspace dependency rule\n\nThe CLI depends on the SDK through a SemVer range. SemVer deliberately excludes\nprereleases unless the comparator names a prerelease with the same base version.\nFor example, `>=0.13.0` does not match `0.14.0-preview.1`.\n\nFor every committed preview version, set both the CLI manifest and lockfile\ndependency floor to that exact preview:\n\n```bash\nnpm pkg set \"dependencies.@bradygaster\u002Fsquad-sdk=>=$VERSION\" \\\n  --workspace @bradygaster\u002Fsquad-cli\nnpm install --package-lock-only\n```\n\nFor `VERSION=0.14.0-preview.1`, the required range is\n`>=0.14.0-preview.1`. Before stable promotion, change the version and floor to\n`0.14.0` \u002F `>=0.14.0`; never leave a prerelease floor in a stable release.\n\nThis rule prevents the PR #640 failure mode, where the build succeeded against\na stale published SDK rather than the workspace SDK.\n\n## 4. Local build versions are ephemeral\n\n`scripts\u002Fbump-build.mjs` may create `-build.N` versions for local development.\n\n- Never commit a `-build.N` version.\n- The script skips itself when `CI=true` or `SKIP_BUILD_BUMP=1`.\n- If a build changes manifests locally, restore the intended release source\n  versions before committing.\n\n## 5. Release lifecycle\n\n1. On a release-preparation branch from `dev`, set the next\n   `X.Y.Z-preview.N` version and matching SDK dependency floor.\n2. Merge to `dev`, wait for CI, and dispatch `squad-release.yml` from `dev`.\n3. Repeat with a new immutable preview version when another candidate is needed.\n4. Dispatch `squad-insider-publish.yml` whenever an on-demand development\n   snapshot is needed; it computes the next immutable `X.Y.Z-insider.N`.\n5. Prepare stable `X.Y.Z` and its stable SDK dependency floor on `dev`.\n6. Dispatch `squad-promote.yml`; it sanitizes `dev`, pushes `main`, and\n   explicitly dispatches the stable release.\n7. Open the next preview-version PR for continued development.\n\nA preview such as `0.14.0-preview.1` is never renamed or converted in place.\nStable `0.14.0` is a separate immutable package version and GitHub tag.\n\n## 6. Ownership\n\nThe current Release Manager owns release version changes. Other agents may update\nversions only when explicitly assigned release work or when reverting an\naccidentally committed local `-build.N` version.\n\n## 7. CI enforcement\n\nCI verifies:\n\n- root, SDK, and CLI versions match;\n- package-lock workspace versions match;\n- committed prereleases use approved `preview` or `insider` identifiers;\n- a preview CLI dependency and lockfile entry equal `>=VERSION`;\n- stable source does not retain a prerelease dependency floor; and\n- workspace packages resolve through local links rather than stale registry\n  packages.\n\nRelease workflows repeat the dependency checks before creating a tag or\npublishing.\n\n## Quick reference\n\n| Rule | Summary |\n|---|---|\n| Insider | The workflow generates `X.Y.Z-insider.N` from the stable base version |\n| Preview | Commit `X.Y.Z-preview.N` to `dev` for an on-demand prerelease |\n| Stable | Only `X.Y.Z` may release from `main` |\n| Sync | Root, SDK, CLI, and lockfile workspace versions must match |\n| Dependency | Preview CLI range and lockfile entry must be `>=VERSION` |\n| Local build | `-build.N` is local-only and never committed |\n| Ownership | The current Release Manager owns planned release version changes |\n",{"name":5,"domain":44,"source":45,"confidence":24,"description":7},"release, versioning, npm, CI","earned (PR #640 workspace resolution incident and automated release channels)","dev","7b731ec97f35346bdc4fa87c3edaf16b808fc0ae","packages\u002Fsquad-sdk\u002Ftemplates\u002Fskills\u002Fversioning-policy",520,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad","https:\u002F\u002Fgithub.github.io\u002Fsquad\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 02:13:59",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add github\u002Fsquad --skill versioning-policy",{"tool":62,"command":63},"bunx","bunx skills add github\u002Fsquad --skill versioning-policy",{"tool":65,"command":66},"pnpm","pnpm dlx skills add github\u002Fsquad --skill versioning-policy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fpackages\u002Fsquad-sdk\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",true,[],[71,79,84,91,98,104],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M76752CVNE7K6NWD59CRAYNJ","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":80,"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":81,"categories":82,"keywords":83,"publishedAt":78},"01M767508W8A4G83NX1FKEW5VN","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":78},"01M7674X5JJKNJ74B3SS8PGXG2","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":78},"01M7674V3S9H03A76H75M1KSAF","test-discipline","Design assertions that prove the actual contract and fail on realistic regressions","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[],[],{"skillNo":99,"name":37,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":78},"01M7674QB8CA61RNDX2Z0NAK71","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\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fsquad\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":78},"01M7674KTQ632N30HQB1TP7TXH","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\u002Fsquad\u002Fblob\u002Fdev\u002Fplugins\u002Fsquad\u002Fskills\u002Fsquad-version-check\u002FSKILL.md",[],[]]