[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADB5R2NWW71Z4CFAD4DCGF":3,"skill-same:01M6ADB5R2NWW71Z4CFAD4DCGF":60},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6ADB5R2NWW71Z4CFAD4DCGF","release-process",null,"Pre-release validation, npm publish procedures, and post-publish verification","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\u002Frelease-process\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"release process","release","process","validation","verification","npm","publish","post","high","release validation","npm publish","2026-11-10 10:12:30",false,"---\nname: \"release-process\"\ndescription: \"Pre-release validation, npm publish procedures, and post-publish verification\"\ndomain: \"release\"\nconfidence: \"high\"\nsource: \"earned\"\n---\n\n# Release Process\n\n> Earned knowledge from the v0.9.0→v0.9.1 and v0.9.4 incidents. Every agent involved in releases MUST read this before starting release work.\n> See also: `.github\u002Fskills\u002Frelease-process\u002FSKILL.md` for the Copilot-facing runbook.\n\n## SCOPE\n\n✅ THIS SKILL PRODUCES:\n- Pre-release validation checks that prevent broken publishes\n- Correct npm publish commands (never workspace-scoped)\n- Fallback procedures when CI workflows fail\n- Post-publish verification steps\n\n❌ THIS SKILL DOES NOT PRODUCE:\n- Feature implementation or test code\n- Architecture decisions\n- Documentation content\n\n## Confidence: high\n\nEstablished through the v0.9.1 incident (8-hour recovery) and reinforced by the v0.9.4 release delay (PRs #1042, #1043, #1044). Every rule below is battle-tested.\n\n## Context\n\nSquad publishes two npm packages: `@bradygaster\u002Fsquad-sdk` and `@bradygaster\u002Fsquad-cli`. The release pipeline flows: dev → preview → main → GitHub Release → npm publish. Brady (project owner) triggers releases — the coordinator does NOT.\n\n## Rules (Non-Negotiable)\n\n### 1. Coordinator Does NOT Publish\n\nThe coordinator routes work and manages agents. It does NOT run `npm publish`, trigger release workflows, or make release decisions. Brady owns the release trigger. If an agent or the coordinator is asked to publish, escalate to Brady.\n\n### 2. Pre-Publish Dependency Validation\n\nBefore ANY release is tagged, scan every `packages\u002F*\u002Fpackage.json` for:\n- `file:` references (workspace leak — the v0.9.0 root cause)\n- `link:` references\n- Absolute paths in dependency values\n- Non-semver version strings\n\n**Command:**\n```bash\ngrep -r '\"file:\\|\"link:\\|\"\u002F' packages\u002F*\u002Fpackage.json\n```\nIf anything matches, STOP. Do not proceed. Fix the reference first.\n\n### 3. Never Use `npm -w` for Publishing\n\n`npm -w packages\u002Fsquad-sdk publish` hangs silently when 2FA is enabled. Always `cd` into the package directory:\n\n```bash\ncd packages\u002Fsquad-sdk && npm publish --access public\ncd packages\u002Fsquad-cli && npm publish --access public\n```\n\n### 4. Fallback Protocol\n\nIf `workflow_dispatch` or the publish workflow fails:\n1. Try once more (ONE retry, not four)\n2. If it fails again → local publish immediately\n3. Do NOT attempt GitHub UI file operations to fix workflow indexing\n4. GitHub has a ~15min workflow cache TTL after file renames\u002Fdeletes — waiting helps, retrying doesn't\n\n### 5. Post-Publish Smoke Test\n\nAfter every publish, verify in a clean shell:\n```bash\nnpm install -g @bradygaster\u002Fsquad-cli@latest\nsquad --version    # should match published version\nsquad doctor       # should pass in a test repo\n```\n\nIf the smoke test fails, rollback immediately.\n\n### 6. npm Token Must Be Automation Type\n\nNPM_TOKEN in CI must be an Automation token (not a user token with 2FA prompts). User tokens with `auth-and-writes` 2FA cause silent hangs in non-interactive environments.\n\n### 7. No Draft GitHub Releases\n\nNever create draft GitHub Releases. The `release: published` event only fires when a release is published — drafts don't trigger the npm publish workflow.\n\n### 8. Version Format\n\nSemantic versioning only: `MAJOR.MINOR.PATCH` (e.g., `0.9.1`). Four-part versions like `0.8.21.4` are NOT valid semver and will break npm publish.\n\n### 9. SKIP_BUILD_BUMP=1 in CI\n\nSet this environment variable in all CI build steps to prevent the build script from mutating versions during CI runs.\n\n## Release Checklist (Quick Reference)\n\n```\n□ All tests passing on dev\n□ No file:\u002Flink: references in packages\u002F*\u002Fpackage.json\n□ Root package.json version matches sub-packages (v0.9.4 lesson — PR #1043)\n□ CHANGELOG.md has ## [$VERSION] section (not just [Unreleased]) (v0.9.4 lesson — PR #1042)\n□ Version bumps committed: npm version $VERSION --workspaces --include-workspace-root --no-git-tag-version\n□ npm auth verified (Automation token)\n□ No draft GitHub Releases pending\n□ Local build + test: npm run build && npx vitest run\n□ Push dev → CI green\n□ Promote dev → preview (squad-promote workflow)\n□ Preview CI green (squad-preview validates)\n□ Promote preview → main\n□ squad-release auto-creates GitHub Release\n□ squad-npm-publish auto-triggers (⚠️ may be BLOCKED — see GITHUB_TOKEN limitation below)\n□ If publish didn't trigger: gh workflow run squad-npm-publish.yml --ref main -f version=X.Y.Z\n□ Monitor publish workflow\n□ Post-publish smoke test\n```\n\n## Known Gotchas\n\n| Gotcha | Impact | Mitigation |\n|--------|--------|------------|\n| npm workspaces rewrite `\"*\"` → `\"file:..\u002Fpath\"` | Broken global installs | Preflight scan in CI (squad-npm-publish.yml) |\n| GitHub Actions workflow cache (~15min TTL) | 422 on workflow_dispatch after file renames | Wait 15min or use local publish fallback |\n| `npm -w publish` hangs with 2FA | Silent hang, no error | Never use `-w` for publish |\n| Draft GitHub Releases | npm publish workflow doesn't trigger | Never create drafts |\n| User npm tokens with 2FA | EOTP errors in CI | Use Automation token type |\n| Root package.json version drift (v0.9.4) | squad-release.yml fails CHANGELOG check | Always bump all 3 package.json files together (PR #1043) |\n| CHANGELOG.md missing `## [$VERSION]` (v0.9.4) | squad-release.yml exits with error | Convert `[Unreleased]` → `[$VERSION] - YYYY-MM-DD` before promoting to main (PR #1042) |\n| GITHUB_TOKEN can't trigger downstream workflows (v0.9.4) | squad-npm-publish.yml never fires | Manual `gh workflow run` or use PAT\u002FGitHub App token (see below) |\n| Lockfile integrity check rejects workspace packages (v0.9.4) | False failures in squad-npm-publish.yml | Only validate packages resolved from npm registry (`startsWith('https:\u002F\u002F')`) (PR #1044) |\n| `prebuild` version bump breaks workspace linking (v0.9.4) | Local builds fail after bump-build.mjs runs | `git checkout -- package.json packages\u002F*\u002Fpackage.json` then fresh install |\n\n## v0.9.4 Incident Learnings\n\n> Source: v0.9.4 release session. PRs #1042, #1043, #1044.\n\n### Root Package.json Version Must Match Sub-Packages\n\n`squad-release.yml` reads version from ROOT `package.json` (lines 31-35):\n```bash\nVERSION=$(node -e \"console.log(require('.\u002Fpackage.json').version)\")\nif ! grep -q \"## \\[$VERSION\\]\" CHANGELOG.md; then\n  echo \"::error::Version $VERSION not found in CHANGELOG.md\"\n  exit 1\nfi\n```\nIf root package.json is behind (e.g., 0.9.1 while sub-packages are 0.9.4), the release workflow FAILS. This was the root cause of the v0.9.4 release delay — PR #1043 fixed it.\n\n**Rule:** When bumping versions, ALWAYS bump all 3 package.json files together:\n```bash\nnpm version $VERSION --workspaces --include-workspace-root --no-git-tag-version\n```\n\n### CHANGELOG.md Must Have Version Entry\n\n`squad-release.yml` validates that `CHANGELOG.md` contains `## [$VERSION]`. If the version section is still `[Unreleased]` and no `[$VERSION]` section exists, the release workflow exits with error. PR #1042 fixed this for v0.9.4.\n\n**Rule:** Before promoting to main, convert `[Unreleased]` to `[$VERSION] - YYYY-MM-DD` in CHANGELOG.md and add a fresh `[Unreleased]` section above it.\n\n### GITHUB_TOKEN Event Propagation Limitation (CRITICAL)\n\nWhen `squad-release.yml` creates a GitHub Release using the default `GITHUB_TOKEN`, the `release: published` event does NOT trigger `squad-npm-publish.yml`. This is a GitHub security feature to prevent infinite workflow loops.\n\n**Workaround:** After the release workflow succeeds and creates the tag + GitHub Release, manually trigger the publish workflow:\n```bash\ngh workflow run squad-npm-publish.yml --ref main -f version=X.Y.Z\n```\nIMPORTANT: Use `--ref main` to ensure the workflow runs against the main branch (where the release artifacts exist).\n\n**Permanent fix (TODO):** Use a PAT or GitHub App token in `squad-release.yml` instead of `GITHUB_TOKEN`.\n\n### Lockfile Integrity — Workspace Package Handling\n\nThe lockfile stability check in `squad-npm-publish.yml` (line 82) filters packages for integrity hashes. Workspace packages resolve to bare relative paths (e.g., `packages\u002Fsquad-sdk`), NOT `file:` URLs. The check must filter for registry-resolved packages only (`startsWith('https:\u002F\u002F')`). PR #1044 fixed this.\n\n### Prebuild Version Bump Breaks Local Workspace Resolution\n\n`scripts\u002Fbump-build.mjs` runs during `npm run prebuild` and bumps versions like `0.9.4` → `0.9.4-build.1`. This breaks workspace linking because CLI depends on exact `\"@bradygaster\u002Fsquad-sdk\": \"0.9.4\"` but SDK becomes `0.9.4-build.1`.\n\n**Fix for local dev:**\n```bash\ngit checkout -- package.json packages\u002F*\u002Fpackage.json\nrm -rf node_modules packages\u002F*\u002Fnode_modules\nnpm install\nnpm run build\n```\n\n### The Full Promotion Chain (v0.9.4 Documented)\n\n```\ndev → preview → main (via squad-promote.yml)\nmain push → squad-release.yml validates CHANGELOG, creates tag + GitHub Release\nrelease published → squad-npm-publish.yml (⚠️ BLOCKED by GITHUB_TOKEN limitation)\nmanual workaround → gh workflow run squad-npm-publish.yml --ref main -f version=X.Y.Z\n```\n\n### npm Publish Workflow Dispatch Target\n\nWhen using `workflow_dispatch` to trigger `squad-npm-publish.yml`, the default ref is the repo's default branch (`dev`). Always specify `--ref main` explicitly to ensure the workflow runs against the branch with the release tag and latest workflow fixes.\n\n## CI Gate: Workspace Publish Policy\n\nThe `publish-policy` job in `squad-ci.yml` scans all workflow files for bare `npm publish` commands that are missing `-w`\u002F`--workspace` flags. Any workflow that attempts a non-workspace-scoped publish will fail CI. This prevents accidental root-level publishes that would push the wrong `package.json` to npm.\n\nSee `.github\u002Fworkflows\u002Fsquad-ci.yml` → `publish-policy` job for implementation details.\n\n## Related\n\n- Issues: #556–#564 (release:next)\n- v0.9.4 fixes: PR #1042 (CHANGELOG), PR #1043 (root package.json), PR #1044 (lockfile integrity)\n- Retro: `.squad\u002Fdecisions\u002Finbox\u002Fsurgeon-v091-retrospective.md`\n- CI audit: `.squad\u002Fdecisions\u002Finbox\u002Fbooster-ci-audit.md`\n- Copilot-level skill: `.github\u002Fskills\u002Frelease-process\u002FSKILL.md`\n- Playbook: `PUBLISH-README.md` (repo root)\n","# Release Process\n\n> Earned knowledge from the v0.9.0→v0.9.1 and v0.9.4 incidents. Every agent involved in releases MUST read this before starting release work.\n> See also: `.github\u002Fskills\u002Frelease-process\u002FSKILL.md` for the Copilot-facing runbook.\n\n## SCOPE\n\n✅ THIS SKILL PRODUCES:\n- Pre-release validation checks that prevent broken publishes\n- Correct npm publish commands (never workspace-scoped)\n- Fallback procedures when CI workflows fail\n- Post-publish verification steps\n\n❌ THIS SKILL DOES NOT PRODUCE:\n- Feature implementation or test code\n- Architecture decisions\n- Documentation content\n\n## Confidence: high\n\nEstablished through the v0.9.1 incident (8-hour recovery) and reinforced by the v0.9.4 release delay (PRs #1042, #1043, #1044). Every rule below is battle-tested.\n\n## Context\n\nSquad publishes two npm packages: `@bradygaster\u002Fsquad-sdk` and `@bradygaster\u002Fsquad-cli`. The release pipeline flows: dev → preview → main → GitHub Release → npm publish. Brady (project owner) triggers releases — the coordinator does NOT.\n\n## Rules (Non-Negotiable)\n\n### 1. Coordinator Does NOT Publish\n\nThe coordinator routes work and manages agents. It does NOT run `npm publish`, trigger release workflows, or make release decisions. Brady owns the release trigger. If an agent or the coordinator is asked to publish, escalate to Brady.\n\n### 2. Pre-Publish Dependency Validation\n\nBefore ANY release is tagged, scan every `packages\u002F*\u002Fpackage.json` for:\n- `file:` references (workspace leak — the v0.9.0 root cause)\n- `link:` references\n- Absolute paths in dependency values\n- Non-semver version strings\n\n**Command:**\n```bash\ngrep -r '\"file:\\|\"link:\\|\"\u002F' packages\u002F*\u002Fpackage.json\n```\nIf anything matches, STOP. Do not proceed. Fix the reference first.\n\n### 3. Never Use `npm -w` for Publishing\n\n`npm -w packages\u002Fsquad-sdk publish` hangs silently when 2FA is enabled. Always `cd` into the package directory:\n\n```bash\ncd packages\u002Fsquad-sdk && npm publish --access public\ncd packages\u002Fsquad-cli && npm publish --access public\n```\n\n### 4. Fallback Protocol\n\nIf `workflow_dispatch` or the publish workflow fails:\n1. Try once more (ONE retry, not four)\n2. If it fails again → local publish immediately\n3. Do NOT attempt GitHub UI file operations to fix workflow indexing\n4. GitHub has a ~15min workflow cache TTL after file renames\u002Fdeletes — waiting helps, retrying doesn't\n\n### 5. Post-Publish Smoke Test\n\nAfter every publish, verify in a clean shell:\n```bash\nnpm install -g @bradygaster\u002Fsquad-cli@latest\nsquad --version    # should match published version\nsquad doctor       # should pass in a test repo\n```\n\nIf the smoke test fails, rollback immediately.\n\n### 6. npm Token Must Be Automation Type\n\nNPM_TOKEN in CI must be an Automation token (not a user token with 2FA prompts). User tokens with `auth-and-writes` 2FA cause silent hangs in non-interactive environments.\n\n### 7. No Draft GitHub Releases\n\nNever create draft GitHub Releases. The `release: published` event only fires when a release is published — drafts don't trigger the npm publish workflow.\n\n### 8. Version Format\n\nSemantic versioning only: `MAJOR.MINOR.PATCH` (e.g., `0.9.1`). Four-part versions like `0.8.21.4` are NOT valid semver and will break npm publish.\n\n### 9. SKIP_BUILD_BUMP=1 in CI\n\nSet this environment variable in all CI build steps to prevent the build script from mutating versions during CI runs.\n\n## Release Checklist (Quick Reference)\n\n```\n□ All tests passing on dev\n□ No file:\u002Flink: references in packages\u002F*\u002Fpackage.json\n□ Root package.json version matches sub-packages (v0.9.4 lesson — PR #1043)\n□ CHANGELOG.md has ## [$VERSION] section (not just [Unreleased]) (v0.9.4 lesson — PR #1042)\n□ Version bumps committed: npm version $VERSION --workspaces --include-workspace-root --no-git-tag-version\n□ npm auth verified (Automation token)\n□ No draft GitHub Releases pending\n□ Local build + test: npm run build && npx vitest run\n□ Push dev → CI green\n□ Promote dev → preview (squad-promote workflow)\n□ Preview CI green (squad-preview validates)\n□ Promote preview → main\n□ squad-release auto-creates GitHub Release\n□ squad-npm-publish auto-triggers (⚠️ may be BLOCKED — see GITHUB_TOKEN limitation below)\n□ If publish didn't trigger: gh workflow run squad-npm-publish.yml --ref main -f version=X.Y.Z\n□ Monitor publish workflow\n□ Post-publish smoke test\n```\n\n## Known Gotchas\n\n| Gotcha | Impact | Mitigation |\n|--------|--------|------------|\n| npm workspaces rewrite `\"*\"` → `\"file:..\u002Fpath\"` | Broken global installs | Preflight scan in CI (squad-npm-publish.yml) |\n| GitHub Actions workflow cache (~15min TTL) | 422 on workflow_dispatch after file renames | Wait 15min or use local publish fallback |\n| `npm -w publish` hangs with 2FA | Silent hang, no error | Never use `-w` for publish |\n| Draft GitHub Releases | npm publish workflow doesn't trigger | Never create drafts |\n| User npm tokens with 2FA | EOTP errors in CI | Use Automation token type |\n| Root package.json version drift (v0.9.4) | squad-release.yml fails CHANGELOG check | Always bump all 3 package.json files together (PR #1043) |\n| CHANGELOG.md missing `## [$VERSION]` (v0.9.4) | squad-release.yml exits with error | Convert `[Unreleased]` → `[$VERSION] - YYYY-MM-DD` before promoting to main (PR #1042) |\n| GITHUB_TOKEN can't trigger downstream workflows (v0.9.4) | squad-npm-publish.yml never fires | Manual `gh workflow run` or use PAT\u002FGitHub App token (see below) |\n| Lockfile integrity check rejects workspace packages (v0.9.4) | False failures in squad-npm-publish.yml | Only validate packages resolved from npm registry (`startsWith('https:\u002F\u002F')`) (PR #1044) |\n| `prebuild` version bump breaks workspace linking (v0.9.4) | Local builds fail after bump-build.mjs runs | `git checkout -- package.json packages\u002F*\u002Fpackage.json` then fresh install |\n\n## v0.9.4 Incident Learnings\n\n> Source: v0.9.4 release session. PRs #1042, #1043, #1044.\n\n### Root Package.json Version Must Match Sub-Packages\n\n`squad-release.yml` reads version from ROOT `package.json` (lines 31-35):\n```bash\nVERSION=$(node -e \"console.log(require('.\u002Fpackage.json').version)\")\nif ! grep -q \"## \\[$VERSION\\]\" CHANGELOG.md; then\n  echo \"::error::Version $VERSION not found in CHANGELOG.md\"\n  exit 1\nfi\n```\nIf root package.json is behind (e.g., 0.9.1 while sub-packages are 0.9.4), the release workflow FAILS. This was the root cause of the v0.9.4 release delay — PR #1043 fixed it.\n\n**Rule:** When bumping versions, ALWAYS bump all 3 package.json files together:\n```bash\nnpm version $VERSION --workspaces --include-workspace-root --no-git-tag-version\n```\n\n### CHANGELOG.md Must Have Version Entry\n\n`squad-release.yml` validates that `CHANGELOG.md` contains `## [$VERSION]`. If the version section is still `[Unreleased]` and no `[$VERSION]` section exists, the release workflow exits with error. PR #1042 fixed this for v0.9.4.\n\n**Rule:** Before promoting to main, convert `[Unreleased]` to `[$VERSION] - YYYY-MM-DD` in CHANGELOG.md and add a fresh `[Unreleased]` section above it.\n\n### GITHUB_TOKEN Event Propagation Limitation (CRITICAL)\n\nWhen `squad-release.yml` creates a GitHub Release using the default `GITHUB_TOKEN`, the `release: published` event does NOT trigger `squad-npm-publish.yml`. This is a GitHub security feature to prevent infinite workflow loops.\n\n**Workaround:** After the release workflow succeeds and creates the tag + GitHub Release, manually trigger the publish workflow:\n```bash\ngh workflow run squad-npm-publish.yml --ref main -f version=X.Y.Z\n```\nIMPORTANT: Use `--ref main` to ensure the workflow runs against the main branch (where the release artifacts exist).\n\n**Permanent fix (TODO):** Use a PAT or GitHub App token in `squad-release.yml` instead of `GITHUB_TOKEN`.\n\n### Lockfile Integrity — Workspace Package Handling\n\nThe lockfile stability check in `squad-npm-publish.yml` (line 82) filters packages for integrity hashes. Workspace packages resolve to bare relative paths (e.g., `packages\u002Fsquad-sdk`), NOT `file:` URLs. The check must filter for registry-resolved packages only (`startsWith('https:\u002F\u002F')`). PR #1044 fixed this.\n\n### Prebuild Version Bump Breaks Local Workspace Resolution\n\n`scripts\u002Fbump-build.mjs` runs during `npm run prebuild` and bumps versions like `0.9.4` → `0.9.4-build.1`. This breaks workspace linking because CLI depends on exact `\"@bradygaster\u002Fsquad-sdk\": \"0.9.4\"` but SDK becomes `0.9.4-build.1`.\n\n**Fix for local dev:**\n```bash\ngit checkout -- package.json packages\u002F*\u002Fpackage.json\nrm -rf node_modules packages\u002F*\u002Fnode_modules\nnpm install\nnpm run build\n```\n\n### The Full Promotion Chain (v0.9.4 Documented)\n\n```\ndev → preview → main (via squad-promote.yml)\nmain push → squad-release.yml validates CHANGELOG, creates tag + GitHub Release\nrelease published → squad-npm-publish.yml (⚠️ BLOCKED by GITHUB_TOKEN limitation)\nmanual workaround → gh workflow run squad-npm-publish.yml --ref main -f version=X.Y.Z\n```\n\n### npm Publish Workflow Dispatch Target\n\nWhen using `workflow_dispatch` to trigger `squad-npm-publish.yml`, the default ref is the repo's default branch (`dev`). Always specify `--ref main` explicitly to ensure the workflow runs against the branch with the release tag and latest workflow fixes.\n\n## CI Gate: Workspace Publish Policy\n\nThe `publish-policy` job in `squad-ci.yml` scans all workflow files for bare `npm publish` commands that are missing `-w`\u002F`--workspace` flags. Any workflow that attempts a non-workspace-scoped publish will fail CI. This prevents accidental root-level publishes that would push the wrong `package.json` to npm.\n\nSee `.github\u002Fworkflows\u002Fsquad-ci.yml` → `publish-policy` job for implementation details.\n\n## Related\n\n- Issues: #556–#564 (release:next)\n- v0.9.4 fixes: PR #1042 (CHANGELOG), PR #1043 (root package.json), PR #1044 (lockfile integrity)\n- Retro: `.squad\u002Fdecisions\u002Finbox\u002Fsurgeon-v091-retrospective.md`\n- CI audit: `.squad\u002Fdecisions\u002Finbox\u002Fbooster-ci-audit.md`\n- Copilot-level skill: `.github\u002Fskills\u002Frelease-process\u002FSKILL.md`\n- Playbook: `PUBLISH-README.md` (repo root)\n",{"name":5,"domain":20,"source":35,"confidence":27,"description":7},"earned","main","8541229759617347888641eba917d3b0ad66a984",".squad\u002Ftemplates\u002Fskills\u002Frelease-process",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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add github\u002Fgh-aw --skill release-process",{"tool":52,"command":53},"bunx","bunx skills add github\u002Fgh-aw --skill release-process",{"tool":55,"command":56},"pnpm","pnpm dlx skills add github\u002Fgh-aw --skill release-process","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Frelease-process\u002FSKILL.md",true,[],[61,90,107,130,156,174],{"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":75,"publishedAt":30},"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",[67,72],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000023","Skill与智能体开发",[9,76,77,78,79,80,81,82,83,84,85,86,87,88,89],"agentic","agentic workflows","github agentic workflows","workflows","github cli","gh","extension","for","compiling","cli","writing","actions","github actions","markdown",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":30},"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",[],[97,98,99,100,101,27,102,103,104,105,106],"windows","windows compatibility","compatibility","bugs","path","platform","cross-platform","patterns","command","git",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":30},"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",[],[114,115,116,117,118,119,120,121,122,123,124,24,125,20,126,127,83,128,85,129],"policy","versioning policy","versioning","incident","gate","implementation","version","Rules","workspace","pr","ci","semver","squad","resolution","incidents","sdk",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":140,"publishedAt":30},"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",[136,139],{"categoryNo":137,"categoryName":138,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[141,142,143,144,83,145,146,147,148,149,150,151,152,153,154,155],"tiered memory","memory","memory-management","model","cold","proposal","runtime","three","spawn","management","context","wiki","agent memory","performance","design",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":165,"publishedAt":30},"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",[162],{"categoryNo":163,"categoryName":164,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000008","测试与质量",[166,167,168,169,170,27,171,117,172,173],"test discipline","discipline","test","sync","when","tests","quality","update",{"skillNo":175,"name":126,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":30},"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",[],[126,180,181,182,183,184,185,186,187,188,189,190,191,105,144,192,193,194,195,196,197,198,85],"show","interactive menu","invoke","coordinator","as","commands","upgrade","options","me","natural language","do","install","team","show me","plugins","issues","state","squad commands","sessions"]