[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75C5B3CSKJS6YCB9NCYJ9G2":3,"skill-same:01M75C5B3CSKJS6YCB9NCYJ9G2":45},{"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":6,"updatedAt":30,"install":31,"resources":44},"01M75C5B3CSKJS6YCB9NCYJ9G2","publish",null,"Cut and ship a new versioned release of this VS Code extension — bump the version, write release notes, run a mandatory safety review of what actually gets packaged, then tag so the GitHub Action packages the VSIX and publishes to the Marketplace. Use when asked to publish, release, deploy, ship a new version, or cut a release of this extension.","cgaspard\u002Flmstudio-vscode-chat","cgaspard","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F759034?v=4","01M75C57SHKRF7W2M4E032MEYZ","Corey Gaspard","01M75C57TBNQ7F73Q10YFSJE45",11,"MIT","https:\u002F\u002Fgithub.com\u002Fcgaspard\u002Flmstudio-vscode-chat\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpublish\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: publish\ndescription: Cut and ship a new versioned release of this VS Code extension — bump the version, write release notes, run a mandatory safety review of what actually gets packaged, then tag so the GitHub Action packages the VSIX and publishes to the Marketplace. Use when asked to publish, release, deploy, ship a new version, or cut a release of this extension.\n---\n\n# Publish a release\n\nThis extension releases are **tag-driven**: pushing a `vX.Y.Z` tag triggers\n`.github\u002Fworkflows\u002Frelease.yml`, which typechecks, compiles, verifies the\nversion\u002Fnotes, packages the `.vsix`, creates a GitHub Release, and publishes to\nthe VS Code Marketplace (needs the `VSCE_PAT` repo secret). There is no manual\n`vsce publish` from a laptop — do **not** run it; let the Action do it so the\nGitHub Release asset and the Marketplace build are byte-identical.\n\n> Applies to both sibling extensions (`lmstudio-vscode-chat` and\n> `ollama-vscode-chat`) — the flow is identical; only the package name and\n> `lmstudioCode`\u002F`ollamaCode` strings differ.\n\n## Preconditions\n\n- On `main`, working tree clean except the release changes, and `git pull` done.\n- You know the extension id: `node -p \"require('.\u002Fpackage.json').publisher + '.' + require('.\u002Fpackage.json').name\"`.\n- Decide the bump (semver): patch for fixes, minor for features, major for breaks\n  (still `0.x` → minor for features is fine).\n\n## Procedure\n\n### 1. Bump the version\nEdit `version` in `package.json`. It MUST equal the tag (without the `v`) — the\nrelease workflow fails the build otherwise.\n\n### 2. Write the release notes\nCreate `releasenotes\u002F\u003Cversion>.yaml` (see `releasenotes\u002FREADME.md` for the\nschema). Keep each list item on **one physical line** (the renderer uses a\nminimal parser); use `[]` for empty sections. Then dry-run the exact render the\nAction will use and read it:\n```bash\nnode scripts\u002Frender-release-notes.js \u003Cversion>\n```\n\n### 3. ⚠️ Safety review of the PACKAGED contents — MANDATORY, do not skip\nThe single most important step. The `.vscodeignore` decides what ships; a wrong\nline can publish source, tests, internal docs, or secrets to the public\nMarketplace. **Review the actual file list, not your assumptions.**\n\n```bash\nnpx vsce ls          # the EXACT set of files that will be in the .vsix\n```\nConfirm the list contains ONLY:\n- `package.json`, `README.md`, `LICENSE`\n- `dist\u002Fextension.js`, `dist\u002Fwebview\u002Fmain.js` (the bundled output)\n- curated `media\u002F*` that the manifest references (icon, activity icon, styles, sample gif)\n\nThen assert nothing inappropriate leaks (should print \"clean\"):\n```bash\nnpx vsce ls | grep -iE '\\.ts$|\\.map$|\u002Fsrc\u002F|\u002Ftest\u002F|tsconfig|esbuild|out-test|node_modules|\\.vsix$|HANDOFF|secret|token|\\.env' \\\n  && echo '!! REVIEW — unexpected file above' || echo 'clean'\n```\nCross-check `.vscodeignore` still excludes: `src\u002F**`, `test\u002F**`, `**\u002F*.ts`,\n`**\u002F*.map`, `out\u002F**`, `out-test\u002F**`, `esbuild*.js`, `tsconfig*.json`, `.github\u002F**`,\n`scripts\u002F**`, `*.vsix`, `*HANDOFF.md`, internal\u002Fdev docs, `sample-workspace\u002F**`,\nand any dev-only\u002Foriginal media.\n\nScan source + bundle for leaked secrets (the `VSCE_PAT` lives ONLY as a GitHub\nsecret, referenced as `secrets.VSCE_PAT` in the workflow — never in code):\n```bash\ngrep -rInE 'eyJ|-----BEGIN|AKIA[0-9A-Z]{16}|xox[baprs]-|ghp_[A-Za-z0-9]{20,}|VSCE_PAT *=' src dist 2>\u002Fdev\u002Fnull \\\n  | grep -v 'secrets.VSCE_PAT' || echo 'no secrets in src\u002Fdist'\n```\nAlso eyeball the diff for appropriateness: README claims true, no debug\u002FPII\nlogging, no hardcoded hosts\u002Fpaths, no profanity or placeholder text, and the\nbundled `dist\u002F*` is freshly built from the committed source.\n\n### 4. Build + test\n```bash\nnpm run check-types && npm run compile && npm test\n```\n(The release workflow runs check-types + compile; tests are local-only but run\nthem anyway — they cover the reliability logic.)\n\n### 5. Commit\nStage everything (`.gitignore` already excludes `dist\u002F`, `out-test\u002F`, `*.vsix`)\nand confirm no build artifacts are staged:\n```bash\ngit add -A && git status --short\ngit commit -m \"Release v\u003Cversion> — \u003Cone-line summary>\"\n```\n\n### 6. Tag and push\n```bash\ngit push origin main\ngit tag -a v\u003Cversion> -m \"v\u003Cversion>\"\ngit push origin v\u003Cversion>\n```\nPushing the tag is what deploys. Channel selection (see release.yml `prepare`):\n- **ODD minor** (`v0.13.0`) → Marketplace **pre-release** (beta channel; users\n  opt in via \"Switch to Pre-Release Version\"). GitHub Release marked pre-release.\n- **EVEN minor** (`v0.14.0`) → Marketplace stable.\n- A `-suffix` tag (`v0.3.0-rc.1`) creates a GitHub pre-release only and\n  **skips** the Marketplace entirely (Marketplace versions must be plain x.y.z).\n\n### 7. Watch and verify\n```bash\ngh run watch \"$(gh run list --workflow=release.yml --limit 1 --json databaseId -q '.[0].databaseId')\" --exit-status\ngh release view v\u003Cversion> --json tagName,isDraft,isPrerelease,assets\n```\nConfirm the run is green (incl. \"Publish to VS Code Marketplace\"), the GitHub\nRelease has both `\u003Cname>-\u003Cversion>.vsix` and `\u003Cname>.vsix` assets, and — after a\nfew minutes' cache lag — `npx vsce show \u003Cpublisher>.\u003Cname>` shows the new version.\n\n## If something fails\n- **Version\u002Ftag mismatch or missing notes file** → the workflow fails fast and\n  nothing is published. Fix on `main`, delete the bad tag\n  (`git push origin :v\u003Cversion>` and `git tag -d v\u003Cversion>`), re-tag, re-push.\n- **Marketplace publish fails (VSCE_PAT)** → the GitHub Release still exists; add\n  a valid `VSCE_PAT` (Marketplace → Manage → PAT with Marketplace scope) under\n  repo Settings → Secrets → Actions, then re-run the failed job.\n- You cannot \"unpublish\" a version cleanly — only publish a higher patch. So the\n  safety review in step 3 is the real gate.\n","# Publish a release\n\nThis extension releases are **tag-driven**: pushing a `vX.Y.Z` tag triggers\n`.github\u002Fworkflows\u002Frelease.yml`, which typechecks, compiles, verifies the\nversion\u002Fnotes, packages the `.vsix`, creates a GitHub Release, and publishes to\nthe VS Code Marketplace (needs the `VSCE_PAT` repo secret). There is no manual\n`vsce publish` from a laptop — do **not** run it; let the Action do it so the\nGitHub Release asset and the Marketplace build are byte-identical.\n\n> Applies to both sibling extensions (`lmstudio-vscode-chat` and\n> `ollama-vscode-chat`) — the flow is identical; only the package name and\n> `lmstudioCode`\u002F`ollamaCode` strings differ.\n\n## Preconditions\n\n- On `main`, working tree clean except the release changes, and `git pull` done.\n- You know the extension id: `node -p \"require('.\u002Fpackage.json').publisher + '.' + require('.\u002Fpackage.json').name\"`.\n- Decide the bump (semver): patch for fixes, minor for features, major for breaks\n  (still `0.x` → minor for features is fine).\n\n## Procedure\n\n### 1. Bump the version\nEdit `version` in `package.json`. It MUST equal the tag (without the `v`) — the\nrelease workflow fails the build otherwise.\n\n### 2. Write the release notes\nCreate `releasenotes\u002F\u003Cversion>.yaml` (see `releasenotes\u002FREADME.md` for the\nschema). Keep each list item on **one physical line** (the renderer uses a\nminimal parser); use `[]` for empty sections. Then dry-run the exact render the\nAction will use and read it:\n```bash\nnode scripts\u002Frender-release-notes.js \u003Cversion>\n```\n\n### 3. ⚠️ Safety review of the PACKAGED contents — MANDATORY, do not skip\nThe single most important step. The `.vscodeignore` decides what ships; a wrong\nline can publish source, tests, internal docs, or secrets to the public\nMarketplace. **Review the actual file list, not your assumptions.**\n\n```bash\nnpx vsce ls          # the EXACT set of files that will be in the .vsix\n```\nConfirm the list contains ONLY:\n- `package.json`, `README.md`, `LICENSE`\n- `dist\u002Fextension.js`, `dist\u002Fwebview\u002Fmain.js` (the bundled output)\n- curated `media\u002F*` that the manifest references (icon, activity icon, styles, sample gif)\n\nThen assert nothing inappropriate leaks (should print \"clean\"):\n```bash\nnpx vsce ls | grep -iE '\\.ts$|\\.map$|\u002Fsrc\u002F|\u002Ftest\u002F|tsconfig|esbuild|out-test|node_modules|\\.vsix$|HANDOFF|secret|token|\\.env' \\\n  && echo '!! REVIEW — unexpected file above' || echo 'clean'\n```\nCross-check `.vscodeignore` still excludes: `src\u002F**`, `test\u002F**`, `**\u002F*.ts`,\n`**\u002F*.map`, `out\u002F**`, `out-test\u002F**`, `esbuild*.js`, `tsconfig*.json`, `.github\u002F**`,\n`scripts\u002F**`, `*.vsix`, `*HANDOFF.md`, internal\u002Fdev docs, `sample-workspace\u002F**`,\nand any dev-only\u002Foriginal media.\n\nScan source + bundle for leaked secrets (the `VSCE_PAT` lives ONLY as a GitHub\nsecret, referenced as `secrets.VSCE_PAT` in the workflow — never in code):\n```bash\ngrep -rInE 'eyJ|-----BEGIN|AKIA[0-9A-Z]{16}|xox[baprs]-|ghp_[A-Za-z0-9]{20,}|VSCE_PAT *=' src dist 2>\u002Fdev\u002Fnull \\\n  | grep -v 'secrets.VSCE_PAT' || echo 'no secrets in src\u002Fdist'\n```\nAlso eyeball the diff for appropriateness: README claims true, no debug\u002FPII\nlogging, no hardcoded hosts\u002Fpaths, no profanity or placeholder text, and the\nbundled `dist\u002F*` is freshly built from the committed source.\n\n### 4. Build + test\n```bash\nnpm run check-types && npm run compile && npm test\n```\n(The release workflow runs check-types + compile; tests are local-only but run\nthem anyway — they cover the reliability logic.)\n\n### 5. Commit\nStage everything (`.gitignore` already excludes `dist\u002F`, `out-test\u002F`, `*.vsix`)\nand confirm no build artifacts are staged:\n```bash\ngit add -A && git status --short\ngit commit -m \"Release v\u003Cversion> — \u003Cone-line summary>\"\n```\n\n### 6. Tag and push\n```bash\ngit push origin main\ngit tag -a v\u003Cversion> -m \"v\u003Cversion>\"\ngit push origin v\u003Cversion>\n```\nPushing the tag is what deploys. Channel selection (see release.yml `prepare`):\n- **ODD minor** (`v0.13.0`) → Marketplace **pre-release** (beta channel; users\n  opt in via \"Switch to Pre-Release Version\"). GitHub Release marked pre-release.\n- **EVEN minor** (`v0.14.0`) → Marketplace stable.\n- A `-suffix` tag (`v0.3.0-rc.1`) creates a GitHub pre-release only and\n  **skips** the Marketplace entirely (Marketplace versions must be plain x.y.z).\n\n### 7. Watch and verify\n```bash\ngh run watch \"$(gh run list --workflow=release.yml --limit 1 --json databaseId -q '.[0].databaseId')\" --exit-status\ngh release view v\u003Cversion> --json tagName,isDraft,isPrerelease,assets\n```\nConfirm the run is green (incl. \"Publish to VS Code Marketplace\"), the GitHub\nRelease has both `\u003Cname>-\u003Cversion>.vsix` and `\u003Cname>.vsix` assets, and — after a\nfew minutes' cache lag — `npx vsce show \u003Cpublisher>.\u003Cname>` shows the new version.\n\n## If something fails\n- **Version\u002Ftag mismatch or missing notes file** → the workflow fails fast and\n  nothing is published. Fix on `main`, delete the bad tag\n  (`git push origin :v\u003Cversion>` and `git tag -d v\u003Cversion>`), re-tag, re-push.\n- **Marketplace publish fails (VSCE_PAT)** → the GitHub Release still exists; add\n  a valid `VSCE_PAT` (Marketplace → Manage → PAT with Marketplace scope) under\n  repo Settings → Secrets → Actions, then re-run the failed job.\n- You cannot \"unpublish\" a version cleanly — only publish a higher patch. So the\n  safety review in step 3 is the real gate.\n",{"name":5,"description":7},"main","170d3fddf72a8b710ee5fa799f3743a28bdb9fae",".claude\u002Fskills\u002Fpublish",4,"https:\u002F\u002Fgithub.com\u002Fcgaspard\u002Flmstudio-vscode-chat","https:\u002F\u002Fgithub.com\u002Fcgaspard","2026-11-07 23:47:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cgaspard\u002Flmstudio-vscode-chat --skill publish",{"tool":37,"command":38},"bunx","bunx skills add cgaspard\u002Flmstudio-vscode-chat --skill publish",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cgaspard\u002Flmstudio-vscode-chat --skill publish","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcgaspard\u002Flmstudio-vscode-chat\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpublish\u002FSKILL.md",true,[],[46,53,60],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M75C5KP4W7AGJF23WJ9RHARQ","codeword","Use when asked for the project codeword. Explains where the codeword lives.","https:\u002F\u002Fgithub.com\u002Fcgaspard\u002Flmstudio-vscode-chat\u002Fblob\u002Fmain\u002Ftest-integration\u002Fe2e\u002Fworkspace\u002F.opencode\u002Fskill\u002Fcodeword\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75C5H70YG1TA03GM5B307FA","claude-codeword","A Claude Code skill (from .claude\u002Fskills) used by the e2e suite to prove Claude Code skills are discovered.","https:\u002F\u002Fgithub.com\u002Fcgaspard\u002Flmstudio-vscode-chat\u002Fblob\u002Fmain\u002Ftest-integration\u002Fe2e\u002Fworkspace\u002F.claude\u002Fskills\u002Fclaude-codeword\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75C5ETNV1A9CP377NF0HSNW","fibonacci-helper","Use when the user asks to optimize, explain, test, or rewrite the Fibonacci function in app.js — or asks about Fibonacci implementations in general (recursive vs iterative vs memoized, time complexity, edge cases).","https:\u002F\u002Fgithub.com\u002Fcgaspard\u002Flmstudio-vscode-chat\u002Fblob\u002Fmain\u002Fsample-workspace\u002F.opencode\u002Fskill\u002Ffibonacci-helper\u002FSKILL.md",[],[]]