[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMDS12BV804GDXRPB2SG8C":3,"skill-same:01M7DMDS12BV804GDXRPB2SG8C":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7DMDS12BV804GDXRPB2SG8C","dsh-create-upgrade-guide",null,"Use when a deepseek-harness change breaks an externally perceptible surface (CLI, profiles, cordis.yml or settings keys, persisted user data, SDK or wire APIs, published package entry points), or when changing a surface that an unreleased upgrade guide already covers, to write or update docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md.","arzvaak\u002FBharatCode-Harness","arzvaak","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F66210729?v=4","01M7DMD1PNVD1R4C473WYBX88X","01M7DMD1QR8H8QQY7FK14KMMRH",0,"MIT","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002F.agents\u002Fskills\u002Fdsh-create-upgrade-guide\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dsh-create-upgrade-guide\ndescription: Use when a deepseek-harness change breaks an externally perceptible surface (CLI, profiles, cordis.yml or settings keys, persisted user data, SDK or wire APIs, published package entry points), or when changing a surface that an unreleased upgrade guide already covers, to write or update docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md.\n---\n\n# DSH Create Upgrade Guide\n\nAn upgrade guide tells a reader who runs release vT what to change to run the next release. Write it in the change that introduces the break, as soon as the break is recognized; do not defer it to release preparation.\n\n## Scope\n\nWrite a guide only for breaks that someone outside the repository can observe after upgrading:\n\n- `dsh` commands, flags, and profile names;\n- `cordis.yml`, patch, overlay, and settings keys or their accepted values;\n- persisted user data: Session logs, SQLite stores, and user data directories;\n- TypeScript and Python SDK exports, JSON-RPC, HTTP, and ACP messages;\n- published package names and entry points.\n\nPre-stable internal APIs whose consumers are all updated in the same change need no guide. A Session-format change still follows [type acknowledgements](..\u002F..\u002F..\u002Fdocs\u002Fcookbook\u002Freviewing-persistence-type-changes.md); its guide states only the reader's actions and links that record.\n\n## Location\n\n`docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md`\n\n- `\u003Cversion>` is the `version` field of the root `package.json` when you write the guide, for example `v0.1.7-rc.2`. The guide describes the upgrade from that release to the next one.\n- `\u003Citem>` is a kebab-case name of the changed surface, for example `profile-flag-rename`.\n- Each item directory holds exactly `guide.md`, its Chinese counterpart `guide.zh.md`, and the pairing record `guide.i18n.yaml`: no index, no attachments.\n\n## Maintenance\n\nWhile the root version is unchanged, the current version directory describes the delta from vT to current `master`. When a later change touches a surface a guide there covers, update that guide in the same change; delete the guide when the break is reverted. After the version bump, guides in older version directories are frozen; a new break goes into the new version directory. Never write a guide spanning more than one release.\n\n## Format\n\nStart from the [upgrade-guide template](..\u002Fdsh-doc\u002Ftemplates\u002Fupgrade-guide.md). `verify-upgrade-guides` enforces:\n\n- frontmatter with exactly `kind: upgrade-guide` and a one-sentence `description` naming what breaks; add a key only together with its gate check, then backfill every guide;\n- one `#` title, then exactly the `## Change` and `## Migration` sections in `guide.md`, and `## 变更` and `## 迁移` in `guide.zh.md`, in that order;\n- at most 500 words in `guide.md`, frontmatter included.\n\n`Change` states the old and new behavior of the surface and who is affected. `Migration` lists ordered steps that name exact files, keys, commands, or symbols, and states how to confirm the migration worked.\n\nWhen a guide needs more than 500 words, the extra text belongs elsewhere: link source files or symbols instead of restating code, move rationale into an [Agent Note](..\u002F..\u002Fnotes\u002FREADME.md), and turn repeated mechanical steps into a script or `dsh` command that the guide invokes.\n\nFollow [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md). Write the Chinese counterpart in the same change under the [bilingual pairing rules](..\u002F..\u002F..\u002Fdocs\u002FDEVELOPER_GUIDE.md), then record the pair with `pnpm run verify-translation-pairing --write docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md`.\n\n## Verify\n\n```sh\npnpm run verify-upgrade-guides\npnpm run verify-translation-pairing docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md\npnpm run verify-md-links\n```\n","# DSH Create Upgrade Guide\n\nAn upgrade guide tells a reader who runs release vT what to change to run the next release. Write it in the change that introduces the break, as soon as the break is recognized; do not defer it to release preparation.\n\n## Scope\n\nWrite a guide only for breaks that someone outside the repository can observe after upgrading:\n\n- `dsh` commands, flags, and profile names;\n- `cordis.yml`, patch, overlay, and settings keys or their accepted values;\n- persisted user data: Session logs, SQLite stores, and user data directories;\n- TypeScript and Python SDK exports, JSON-RPC, HTTP, and ACP messages;\n- published package names and entry points.\n\nPre-stable internal APIs whose consumers are all updated in the same change need no guide. A Session-format change still follows [type acknowledgements](..\u002F..\u002F..\u002Fdocs\u002Fcookbook\u002Freviewing-persistence-type-changes.md); its guide states only the reader's actions and links that record.\n\n## Location\n\n`docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md`\n\n- `\u003Cversion>` is the `version` field of the root `package.json` when you write the guide, for example `v0.1.7-rc.2`. The guide describes the upgrade from that release to the next one.\n- `\u003Citem>` is a kebab-case name of the changed surface, for example `profile-flag-rename`.\n- Each item directory holds exactly `guide.md`, its Chinese counterpart `guide.zh.md`, and the pairing record `guide.i18n.yaml`: no index, no attachments.\n\n## Maintenance\n\nWhile the root version is unchanged, the current version directory describes the delta from vT to current `master`. When a later change touches a surface a guide there covers, update that guide in the same change; delete the guide when the break is reverted. After the version bump, guides in older version directories are frozen; a new break goes into the new version directory. Never write a guide spanning more than one release.\n\n## Format\n\nStart from the [upgrade-guide template](..\u002Fdsh-doc\u002Ftemplates\u002Fupgrade-guide.md). `verify-upgrade-guides` enforces:\n\n- frontmatter with exactly `kind: upgrade-guide` and a one-sentence `description` naming what breaks; add a key only together with its gate check, then backfill every guide;\n- one `#` title, then exactly the `## Change` and `## Migration` sections in `guide.md`, and `## 变更` and `## 迁移` in `guide.zh.md`, in that order;\n- at most 500 words in `guide.md`, frontmatter included.\n\n`Change` states the old and new behavior of the surface and who is affected. `Migration` lists ordered steps that name exact files, keys, commands, or symbols, and states how to confirm the migration worked.\n\nWhen a guide needs more than 500 words, the extra text belongs elsewhere: link source files or symbols instead of restating code, move rationale into an [Agent Note](..\u002F..\u002Fnotes\u002FREADME.md), and turn repeated mechanical steps into a script or `dsh` command that the guide invokes.\n\nFollow [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md). Write the Chinese counterpart in the same change under the [bilingual pairing rules](..\u002F..\u002F..\u002Fdocs\u002FDEVELOPER_GUIDE.md), then record the pair with `pnpm run verify-translation-pairing --write docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md`.\n\n## Verify\n\n```sh\npnpm run verify-upgrade-guides\npnpm run verify-translation-pairing docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md\npnpm run verify-md-links\n```\n",{"name":5,"description":7},"implementation\u002Fcore-extension-store","091701ca5a621697bf357a7eb654d699468c6200",".agents\u002Fskills\u002Fdsh-create-upgrade-guide","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness","https:\u002F\u002Farzvaak.github.io\u002FBharatCode-Harness\u002F","https:\u002F\u002Fgithub.com\u002Farzvaak","2026-11-07 04:07:44",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add arzvaak\u002FBharatCode-Harness --skill dsh-create-upgrade-guide",{"tool":36,"command":37},"bunx","bunx skills add arzvaak\u002FBharatCode-Harness --skill dsh-create-upgrade-guide",{"tool":39,"command":40},"pnpm","pnpm dlx skills add arzvaak\u002FBharatCode-Harness --skill dsh-create-upgrade-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002F.agents\u002Fskills\u002Fdsh-create-upgrade-guide\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7DMGTGVNV395QREH8KYS1WJ","user-only-skill","Prove model-disabled skills stay outside the model catalog.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fuser-only-skill\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7DMGRX3R4BGDKH3B6S5XBBC","snapshot-skill","Exercise project skill discovery and loading in snapshot tests.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fsnapshot-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7DMGNPK8FC86W4PK3WY28JX","model-only-skill","Prove user-disabled skills remain available to the model.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fmodel-only-skill\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7DMGFS8TJQJN069912Q3CAH","office-xlsx","Read, create, and modify Excel workbooks (.xlsx), including data, formulas, formatting, and pandas analysis. Use for Excel inputs or deliverables. Load before running Office commands. Data and formula tasks skip visual inspection; inspect only for formatting or layout needs. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-xlsx\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7DMGB0TGZWF0Y857P7803ZB","office-pptx","Create, read, edit, and check PowerPoint presentations (.pptx), including slide text, tables, images, and charts. Use when a PPTX file is an input or requested deliverable. Load this skill before running Office commands. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-pptx\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7DMG6VBMAW4Q5BRDR1PBP03","office-docx","Create, read, edit, and check Word documents (.docx), including reports, letters, and formatted tables. Use when a DOCX file is an input or requested deliverable. Load this skill before running Office commands. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-docx\u002FSKILL.md",[],[]]