[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KN97QK80XWGPR613A5JH3Q":3,"skill-same:01M6KN97QK80XWGPR613A5JH3Q":74},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6KN97QK80XWGPR613A5JH3Q","markdown-studio-release-prep",null,"Prepare Markdown Studio VS Code extension releases up to the human handoff point. Use when the user asks to prepare, finalize, close, tag-check, package, or get v1.x ready for release\u002Fpublish, especially before Marketplace publishing, GitHub release tags, VSIX packaging, changelog cleanup, demo PDF artifacts, or release verification.","kino-6\u002Fvscode-markdown-studio","kino-6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F67919233?v=4","01M6KN8XZZWY9FPTJCV9WMYGFB","01M6KN8Y48TWC0HZY9FB50GJYY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkino-6\u002Fvscode-markdown-studio\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmarkdown-studio-release-prep\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"markdown studio release prep","release prep","release","prep","markdown","studio","up","for","v1","tags","get","publishing","PDF","ready","use","packaging","package","artifacts","code","cleanup","2026-11-10 10:12:30",false,"---\nname: markdown-studio-release-prep\ndescription: Prepare Markdown Studio VS Code extension releases up to the human handoff point. Use when the user asks to prepare, finalize, close, tag-check, package, or get v1.x ready for release\u002Fpublish, especially before Marketplace publishing, GitHub release tags, VSIX packaging, changelog cleanup, demo PDF artifacts, or release verification.\n---\n\n# Markdown Studio Release Prep\n\n## Goal\n\nBring this repository to a release-ready handoff state without performing the final human polish or Marketplace publish.\n\nStop before actions that should remain human-owned:\n\n- Do not run `vsce publish` unless the user explicitly asks for publishing.\n- Do not create or push the release tag until changelog, package version, tests, package output, and release impact are explained to the user and the user explicitly approves tagging.\n- Do not rewrite the final marketing copy beyond factual release-note cleanup unless requested.\n\n## Release Handoff Definition\n\nThe handoff is ready when:\n\n- Working tree is clean or only intentionally generated local artifacts are ignored.\n- `package.json` version matches the intended release version.\n- `CHANGELOG.md` has the intended version\u002Fdate section and no release content stranded under `Unreleased`.\n- `examples\u002Fdemo.pdf` is committed when regenerated by release verification.\n- `@vscode\u002Fvsce` is not stale enough to emit package warnings during `npm run package`.\n- Verification commands have passed or failures are clearly documented.\n- `dist\u002Fmarkdown-studio-local-\u003Cversion>.vsix` exists from the latest package run.\n- The current commit is pushed to `origin\u002Fmain`.\n- Tag status is resolved clearly: existing tag verified, tag pending human confirmation, or tag created and pushed after confirmation.\n\n## Workflow\n\n1. Inspect state:\n   - `git status --short --branch`\n   - `node -p \"require('.\u002Fpackage.json').version\"`\n   - `git tag --sort=-v:refname | head -20`\n   - `sed -n '1,80p' CHANGELOG.md`\n\n2. Reconcile release notes:\n   - If `Unreleased` contains items intended for the release, move them into the target version section.\n   - Use the actual release date.\n   - Keep a blank `## [Unreleased]` section only if useful for future work.\n\n3. Verify version and tooling:\n   - Confirm `package.json` and `package-lock.json` agree on the version.\n   - If `npm run package` reports a stale `@vscode\u002Fvsce`, update the local devDependency and lockfile.\n   - Keep dev reinstall warnings suppressed in `scripts\u002Fdev\u002Freinstall.sh` rather than asking repeatedly about `[DEP0169]`.\n\n4. Run verification:\n   - `npm run test:ci`\n   - `npm run test:demo-render`\n   - `npm run test:local-only`\n   - `npm run test:e2e`\n   - `npm run package`\n   - `npm audit --omit=dev --audit-level=high`\n\n5. Treat generated demo artifacts as release artifacts:\n   - If verification regenerates `examples\u002Fdemo.pdf`, stage and commit it with the release changes.\n   - Do not repeatedly ask the user whether to include `examples\u002Fdemo.pdf`; include it unless explicitly told not to.\n\n6. Commit and push:\n   - Review `git diff --stat` and key diffs.\n   - Commit all intended release-prep changes with a concise message.\n   - Push `main` to `origin`.\n\n7. Tag confirmation and automation:\n   - Report the exact release situation before asking for confirmation:\n     - Intended version and tag name, for example `v1.0.3`.\n     - Current commit SHA and whether it is pushed to `origin\u002Fmain`.\n     - Working tree status.\n     - Verification status for tests, demo render, E2E, package, audit, and VSIX output.\n     - Whether the tag already exists locally or on `origin`.\n     - The effect of pushing the tag: `.github\u002Fworkflows\u002Frelease.yml` runs lint, unit, integration, and `test:local-only`, then builds the VSIX and creates the GitHub Release on `v*` tag push. If any check fails, no VSIX or release is produced.\n   - If the tag already exists, verify it points to the intended commit. If it points elsewhere, stop and explain the mismatch.\n   - If the tag is missing and all gates pass, ask for explicit human confirmation such as: `May I create and push v\u003Cversion> now?`\n   - After confirmation, create and push the tag automatically:\n     - `git tag v\u003Cversion>`\n     - `git push origin v\u003Cversion>`\n   - Do not merely hand back tag commands unless the user asks to perform tagging manually.\n\n8. Publish handoff:\n   - Confirm the tag's Release workflow run succeeded (`gh run list --workflow release.yml --limit 1`). If it failed, do not publish: the full checks did not pass for that commit.\n   - Before recommending or running Marketplace publish, verify the stored Marketplace token:\n     - `vsce verify-pat`\n   - If PAT verification fails, stop and explain the failure. Do not publish.\n   - If PAT verification succeeds and tests\u002Fpackage are green, give the final publish command:\n     - `vsce publish`\n   - Run `vsce publish` only when the user explicitly authorizes Marketplace publishing after the PAT and release gates are green.\n   - Leave final Marketplace publish decision to the human unless explicitly authorized.\n\n## Project-Specific Notes\n\n- This repo publishes `kino6.markdown-studio-local`.\n- Release workflow is tag-driven: `.github\u002Fworkflows\u002Frelease.yml` runs on `v*` tags.\n- `npm run package` creates `dist\u002Fmarkdown-studio-local-\u003Cversion>.vsix`.\n- `scripts\u002Fdev\u002Freinstall.sh` is used frequently; keep it quiet and deterministic for local validation.\n- `AGENTS.md` is a repository agent note and must stay excluded from VSIX via `.vscodeignore`.\n","# Markdown Studio Release Prep\n\n## Goal\n\nBring this repository to a release-ready handoff state without performing the final human polish or Marketplace publish.\n\nStop before actions that should remain human-owned:\n\n- Do not run `vsce publish` unless the user explicitly asks for publishing.\n- Do not create or push the release tag until changelog, package version, tests, package output, and release impact are explained to the user and the user explicitly approves tagging.\n- Do not rewrite the final marketing copy beyond factual release-note cleanup unless requested.\n\n## Release Handoff Definition\n\nThe handoff is ready when:\n\n- Working tree is clean or only intentionally generated local artifacts are ignored.\n- `package.json` version matches the intended release version.\n- `CHANGELOG.md` has the intended version\u002Fdate section and no release content stranded under `Unreleased`.\n- `examples\u002Fdemo.pdf` is committed when regenerated by release verification.\n- `@vscode\u002Fvsce` is not stale enough to emit package warnings during `npm run package`.\n- Verification commands have passed or failures are clearly documented.\n- `dist\u002Fmarkdown-studio-local-\u003Cversion>.vsix` exists from the latest package run.\n- The current commit is pushed to `origin\u002Fmain`.\n- Tag status is resolved clearly: existing tag verified, tag pending human confirmation, or tag created and pushed after confirmation.\n\n## Workflow\n\n1. Inspect state:\n   - `git status --short --branch`\n   - `node -p \"require('.\u002Fpackage.json').version\"`\n   - `git tag --sort=-v:refname | head -20`\n   - `sed -n '1,80p' CHANGELOG.md`\n\n2. Reconcile release notes:\n   - If `Unreleased` contains items intended for the release, move them into the target version section.\n   - Use the actual release date.\n   - Keep a blank `## [Unreleased]` section only if useful for future work.\n\n3. Verify version and tooling:\n   - Confirm `package.json` and `package-lock.json` agree on the version.\n   - If `npm run package` reports a stale `@vscode\u002Fvsce`, update the local devDependency and lockfile.\n   - Keep dev reinstall warnings suppressed in `scripts\u002Fdev\u002Freinstall.sh` rather than asking repeatedly about `[DEP0169]`.\n\n4. Run verification:\n   - `npm run test:ci`\n   - `npm run test:demo-render`\n   - `npm run test:local-only`\n   - `npm run test:e2e`\n   - `npm run package`\n   - `npm audit --omit=dev --audit-level=high`\n\n5. Treat generated demo artifacts as release artifacts:\n   - If verification regenerates `examples\u002Fdemo.pdf`, stage and commit it with the release changes.\n   - Do not repeatedly ask the user whether to include `examples\u002Fdemo.pdf`; include it unless explicitly told not to.\n\n6. Commit and push:\n   - Review `git diff --stat` and key diffs.\n   - Commit all intended release-prep changes with a concise message.\n   - Push `main` to `origin`.\n\n7. Tag confirmation and automation:\n   - Report the exact release situation before asking for confirmation:\n     - Intended version and tag name, for example `v1.0.3`.\n     - Current commit SHA and whether it is pushed to `origin\u002Fmain`.\n     - Working tree status.\n     - Verification status for tests, demo render, E2E, package, audit, and VSIX output.\n     - Whether the tag already exists locally or on `origin`.\n     - The effect of pushing the tag: `.github\u002Fworkflows\u002Frelease.yml` runs lint, unit, integration, and `test:local-only`, then builds the VSIX and creates the GitHub Release on `v*` tag push. If any check fails, no VSIX or release is produced.\n   - If the tag already exists, verify it points to the intended commit. If it points elsewhere, stop and explain the mismatch.\n   - If the tag is missing and all gates pass, ask for explicit human confirmation such as: `May I create and push v\u003Cversion> now?`\n   - After confirmation, create and push the tag automatically:\n     - `git tag v\u003Cversion>`\n     - `git push origin v\u003Cversion>`\n   - Do not merely hand back tag commands unless the user asks to perform tagging manually.\n\n8. Publish handoff:\n   - Confirm the tag's Release workflow run succeeded (`gh run list --workflow release.yml --limit 1`). If it failed, do not publish: the full checks did not pass for that commit.\n   - Before recommending or running Marketplace publish, verify the stored Marketplace token:\n     - `vsce verify-pat`\n   - If PAT verification fails, stop and explain the failure. Do not publish.\n   - If PAT verification succeeds and tests\u002Fpackage are green, give the final publish command:\n     - `vsce publish`\n   - Run `vsce publish` only when the user explicitly authorizes Marketplace publishing after the PAT and release gates are green.\n   - Leave final Marketplace publish decision to the human unless explicitly authorized.\n\n## Project-Specific Notes\n\n- This repo publishes `kino6.markdown-studio-local`.\n- Release workflow is tag-driven: `.github\u002Fworkflows\u002Frelease.yml` runs on `v*` tags.\n- `npm run package` creates `dist\u002Fmarkdown-studio-local-\u003Cversion>.vsix`.\n- `scripts\u002Fdev\u002Freinstall.sh` is used frequently; keep it quiet and deterministic for local validation.\n- `AGENTS.md` is a repository agent note and must stay excluded from VSIX via `.vscodeignore`.\n",{"name":5,"description":7},"main","42df7f8f6008ac1017a3c7405591030f33134d0b",".agents\u002Fskills\u002Fmarkdown-studio-release-prep","https:\u002F\u002Fgithub.com\u002Fkino-6\u002Fvscode-markdown-studio","https:\u002F\u002Fgithub.com\u002Fkino-6","2026-10-28 01:18:06",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add kino-6\u002Fvscode-markdown-studio --skill markdown-studio-release-prep",{"tool":60,"command":61},"bunx","bunx skills add kino-6\u002Fvscode-markdown-studio --skill markdown-studio-release-prep",{"tool":63,"command":64},"pnpm","pnpm dlx skills add kino-6\u002Fvscode-markdown-studio --skill markdown-studio-release-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkino-6\u002Fvscode-markdown-studio\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmarkdown-studio-release-prep\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"agents\u002Fopenai.yaml","REFERENCE","参考文档",247,"https:\u002F\u002Fgithub.com\u002Fkino-6\u002Fvscode-markdown-studio\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmarkdown-studio-release-prep\u002Fagents\u002Fopenai.yaml",[75,84,103],{"skillNo":76,"name":77,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":43},"01M6KN9GZ75M7G9BBN6G6X4801","Bad_Name","https:\u002F\u002Fgithub.com\u002Fkino-6\u002Fvscode-markdown-studio\u002Fblob\u002Fmain\u002Ftest\u002Fe2e\u002Ffixtures\u002Fworkspace\u002Fskills\u002FBadName\u002FSKILL.md",[],[81,82,83],"name","bad","bad name",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":94,"publishedAt":43},"01M6KN9CTPWGQZYNAK9PHVXQG8","sample-skill","Summarizes release notes for Markdown Studio. Use when the user asks what changed in a release.","MIT","https:\u002F\u002Fgithub.com\u002Fkino-6\u002Fvscode-markdown-studio\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fsample-skill\u002FSKILL.md",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[95,96,25,97,27,98,99,100,37,101,28,30,102],"sample","sample skill","acceptance","grep","read","user","release notes","notes",{"skillNo":104,"name":77,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":43},"01M6KN9BC86ER007XATQ8RDCY9","https:\u002F\u002Fgithub.com\u002Fkino-6\u002Fvscode-markdown-studio\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002FBadName\u002FSKILL.md",[],[82,81,83]]