[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69B73Q4D72JRA884EAV2M8A":3,"skill-same:01M69B73Q4D72JRA884EAV2M8A":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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M69B73Q4D72JRA884EAV2M8A","emitter-prep-for-pr",null,"Prepare language emitter changes for PR: validate (build, format, lint), add a changeset, and push. This skill is specifically for the language emitter packages (http-client-python, http-client-csharp, http-client-java) - NOT for core TypeSpec packages like compiler, http, openapi3, etc. Use when the user wants to finalize emitter changes, says things like \"prep for pr\", \"prepare for PR\", \"validate and push\", \"add changeset\", or \"finalize changes\".","microsoft\u002Ftypespec","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69B6S8HEDME7WWCNE7RGPJF",5948,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Femitter-prep-for-pr\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"for","pr","prep","emitter prep for pr","lint","when","things","add","use","changeset","compiler","java","push","python","core","csharp","typespec","openapi3","packages","http","prepare","validate","2026-11-10 10:12:30",false,"---\nname: emitter-prep-for-pr\ndescription: >\n  Prepare language emitter changes for PR: validate (build, format, lint), add\n  a changeset, and push. This skill is specifically for the language emitter\n  packages (http-client-python, http-client-csharp, http-client-java) - NOT for\n  core TypeSpec packages like compiler, http, openapi3, etc. Use when the user\n  wants to finalize emitter changes, says things like \"prep for pr\", \"prepare\n  for PR\", \"validate and push\", \"add changeset\", or \"finalize changes\".\n---\n\n# Emitter Prep for PR\n\nPrepares language emitter changes for pull request by running build\u002Fformat\u002Flint,\nchecking for a changeset, and pushing to the remote branch.\n\n**This skill is for language emitter packages only:**\n\n- `http-client-python`\n- `http-client-csharp`\n- `http-client-java`\n\nDo NOT use this skill for core TypeSpec packages (compiler, http, openapi3, etc.).\n\n## Workflow\n\n### Step 1: Determine the emitter package\n\nFigure out which emitter package the user is working on from context (cwd, recent\nchanges, or ask). The package will be under `packages\u002F\u003Cpackage-name>\u002F`.\n\n### Step 2: Build, format, and lint the emitter package\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002FPACKAGE_NAME\n\n# Build\nnpm run build\n\n# Format (includes both TypeScript and Python formatting)\nnpm run format\n\n# Lint (emitter-only is fine for quick validation)\nnpm run lint -- --emitter\n```\n\nIf any step fails, report the error and stop. Do not proceed.\n\n### Step 3: Run format at repo root\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\npnpm format\n```\n\n**Important:** `pnpm format` may touch files outside the emitter package (e.g.,\n`.devcontainer\u002F`, other packages). When staging changes in Step 6, **only stage\nfiles within the emitter package directory** (`packages\u002FPACKAGE_NAME\u002F`) and\n`.chronus\u002Fchanges\u002F` and `.github\u002Fskills\u002F`. Discard any formatting changes to\nunrelated files with `git checkout -- \u003Cfile>`.\n\n### Step 4: Check for existing changeset\n\nCheck if a changeset already exists for the current branch:\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\nls .chronus\u002Fchanges\u002F | grep -i \"$BRANCH\" || echo \"NO_CHANGESET\"\n```\n\n- If a changeset **exists**: Skip to Step 6 (no need to create one).\n- If **NO_CHANGESET**: Proceed to Step 5 to create one.\n\n### Step 5: Create changeset (only if none exists)\n\nAsk the user what kind of change this is, or infer from context:\n\n1. **changeKind** - one of: `internal`, `fix`, `feature`, `deprecation`, `breaking`, `dependencies`\n2. **message** - concise user-focused description\n\nThen create the file:\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\nTIMESTAMP=$(date +\"%Y-%m-%d-%H-%M-%S\")\nFILENAME=\".chronus\u002Fchanges\u002F${BRANCH}-${TIMESTAMP}.md\"\n```\n\n```markdown\n---\nchangeKind: \u003CKIND>\npackages:\n  - \"\u003CPACKAGE>\"\n---\n\n\u003CMESSAGE>\n```\n\n### Step 6: Stage, commit, and push\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\ngit add -A\ngit status\n```\n\nShow the user what will be committed and ask for confirmation. Then:\n\n```bash\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\ngit commit -m \"\u003CCOMMIT_MESSAGE>\n\nCo-authored-by: Copilot \u003C223556219+Copilot@users.noreply.github.com>\"\n\n# Always push to origin (user's fork), never upstream\ngit push origin \"$BRANCH\"\n```\n\n## Changeset Guidelines\n\n### changeKind reference\n\n- **internal**: Tests, CI\u002FCD, refactoring, docs, skills — not user-facing\n- **fix**: Bug fixes users would notice\n- **feature**: New user-facing capabilities\n- **deprecation**: Marking something as deprecated\n- **breaking**: Removing or changing behavior incompatibly\n- **dependencies**: Dependency version bumps\n\n### Message examples\n\n- `internal`: \"Improve CI pipeline performance and test infrastructure\"\n- `fix`: \"Fix incorrect deserialization of nullable enum properties\"\n- `feature`: \"Add support for XML serialization in request bodies\"\n\n### Package names\n\n| Folder               | Package Name                   |\n| -------------------- | ------------------------------ |\n| `http-client-python` | `@typespec\u002Fhttp-client-python` |\n| `http-client-csharp` | `@typespec\u002Fhttp-client-csharp` |\n| `http-client-java`   | `@typespec\u002Fhttp-client-java`   |\n","# Emitter Prep for PR\n\nPrepares language emitter changes for pull request by running build\u002Fformat\u002Flint,\nchecking for a changeset, and pushing to the remote branch.\n\n**This skill is for language emitter packages only:**\n\n- `http-client-python`\n- `http-client-csharp`\n- `http-client-java`\n\nDo NOT use this skill for core TypeSpec packages (compiler, http, openapi3, etc.).\n\n## Workflow\n\n### Step 1: Determine the emitter package\n\nFigure out which emitter package the user is working on from context (cwd, recent\nchanges, or ask). The package will be under `packages\u002F\u003Cpackage-name>\u002F`.\n\n### Step 2: Build, format, and lint the emitter package\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002FPACKAGE_NAME\n\n# Build\nnpm run build\n\n# Format (includes both TypeScript and Python formatting)\nnpm run format\n\n# Lint (emitter-only is fine for quick validation)\nnpm run lint -- --emitter\n```\n\nIf any step fails, report the error and stop. Do not proceed.\n\n### Step 3: Run format at repo root\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\npnpm format\n```\n\n**Important:** `pnpm format` may touch files outside the emitter package (e.g.,\n`.devcontainer\u002F`, other packages). When staging changes in Step 6, **only stage\nfiles within the emitter package directory** (`packages\u002FPACKAGE_NAME\u002F`) and\n`.chronus\u002Fchanges\u002F` and `.github\u002Fskills\u002F`. Discard any formatting changes to\nunrelated files with `git checkout -- \u003Cfile>`.\n\n### Step 4: Check for existing changeset\n\nCheck if a changeset already exists for the current branch:\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\nls .chronus\u002Fchanges\u002F | grep -i \"$BRANCH\" || echo \"NO_CHANGESET\"\n```\n\n- If a changeset **exists**: Skip to Step 6 (no need to create one).\n- If **NO_CHANGESET**: Proceed to Step 5 to create one.\n\n### Step 5: Create changeset (only if none exists)\n\nAsk the user what kind of change this is, or infer from context:\n\n1. **changeKind** - one of: `internal`, `fix`, `feature`, `deprecation`, `breaking`, `dependencies`\n2. **message** - concise user-focused description\n\nThen create the file:\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\nTIMESTAMP=$(date +\"%Y-%m-%d-%H-%M-%S\")\nFILENAME=\".chronus\u002Fchanges\u002F${BRANCH}-${TIMESTAMP}.md\"\n```\n\n```markdown\n---\nchangeKind: \u003CKIND>\npackages:\n  - \"\u003CPACKAGE>\"\n---\n\n\u003CMESSAGE>\n```\n\n### Step 6: Stage, commit, and push\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\ngit add -A\ngit status\n```\n\nShow the user what will be committed and ask for confirmation. Then:\n\n```bash\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\ngit commit -m \"\u003CCOMMIT_MESSAGE>\n\nCo-authored-by: Copilot \u003C223556219+Copilot@users.noreply.github.com>\"\n\n# Always push to origin (user's fork), never upstream\ngit push origin \"$BRANCH\"\n```\n\n## Changeset Guidelines\n\n### changeKind reference\n\n- **internal**: Tests, CI\u002FCD, refactoring, docs, skills — not user-facing\n- **fix**: Bug fixes users would notice\n- **feature**: New user-facing capabilities\n- **deprecation**: Marking something as deprecated\n- **breaking**: Removing or changing behavior incompatibly\n- **dependencies**: Dependency version bumps\n\n### Message examples\n\n- `internal`: \"Improve CI pipeline performance and test infrastructure\"\n- `fix`: \"Fix incorrect deserialization of nullable enum properties\"\n- `feature`: \"Add support for XML serialization in request bodies\"\n\n### Package names\n\n| Folder               | Package Name                   |\n| -------------------- | ------------------------------ |\n| `http-client-python` | `@typespec\u002Fhttp-client-python` |\n| `http-client-csharp` | `@typespec\u002Fhttp-client-csharp` |\n| `http-client-java`   | `@typespec\u002Fhttp-client-java`   |\n",{"name":5,"description":7},"main","05b9bad7c57b9b58e8fb5390f9bab081a1a9ac31",".github\u002Fskills\u002Femitter-prep-for-pr",423,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec","https:\u002F\u002Ftypespec.io\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 06:59:49",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add microsoft\u002Ftypespec --skill emitter-prep-for-pr",{"tool":62,"command":63},"bunx","bunx skills add microsoft\u002Ftypespec --skill emitter-prep-for-pr",{"tool":65,"command":66},"pnpm","pnpm dlx skills add microsoft\u002Ftypespec --skill emitter-prep-for-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Femitter-prep-for-pr\u002FSKILL.md",true,[],[71,103,124,145,176,189],{"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":85,"publishedAt":41},"01M69B7KKBZE845SFNJQ5H992V","test-unbranded-emitter","Build and test the @typespec\u002Fhttp-client-python emitter. Use this skill whenever the user wants to test their local changes to the emitter, run the generator test suite, check if their http-client-python changes are passing, or validate a fix. Triggers on phrases like \"test the emitter\", \"run tests\", \"check if my changes pass\", \"run test:generator\", \"run CI\", or any mention of testing\u002Fvalidating changes in the emitter package.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002Fpackages\u002Fhttp-client-python\u002F.github\u002Fskills\u002Ftest-unbranded-emitter\u002FSKILL.md",[77,82],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发",[86,87,88,32,89,40,90,38,35,91,92,93,94,95,27,96,97,98,99,100,101,102],"test","test unbranded emitter","testing","build and test","run tests","run","package","ci","check","fix","test suite","build","local","tests","triggers","generator","changes",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":110,"publishedAt":41},"01M69B7H23BJ7ART6SA67EFJ5W","generate-from-typespec","Generate Python SDK code from a TypeSpec specification using the local emitter. Use this skill when the user wants to generate\u002Fregenerate a Python client from a TypeSpec spec, provides a GitHub URL or local path to a TypeSpec project, or says things like \"generate from this spec\", \"emit Python from this tsp\", \"regenerate the SDK\", or \"compile this TypeSpec for Python\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002Fpackages\u002Fhttp-client-python\u002F.github\u002Fskills\u002Fgenerate-from-typespec\u002FSKILL.md",[109],{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},[35,111,112,113,32,114,115,116,117,118,119,27,120,98,121,122,123,19,25,24],"generate from typespec","generate","spec","github","sdk","code","compile","python sdk","user","specification","project","client","URL",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":41},"01M69B7EJ0F9HGY2Y8RMX9C4E6","diff-upstream","Regenerate the local emitter and diff the generated code against the upstream baseline checked into autorest.python. Use this skill when the user wants to see how their emitter changes affect generated code compared to what's currently in production, says things like \"diff upstream\", \"compare to baseline\", \"what changed vs production\", \"show me the diff\", \"how does this affect generated code\", or wants to validate their changes produce the expected output differences.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002Fpackages\u002Fhttp-client-python\u002F.github\u002Fskills\u002Fdiff-upstream\u002FSKILL.md",[130],{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},[132,133,134,32,40,116,135,136,137,138,139,27,140,141,98,142,143,25,102,144,24],"diff upstream","diff","upstream","produce","baseline","show me","how","generated","show","me","compare","output","expected",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":165,"publishedAt":41},"01M69B7BHV2RTK64BZ8NQGFPNE","writing-python-sdk-spector-mock-api-tests","Writes TypeSpec http-client-python generator mock API tests (azure\u002Funbranded\u002Fshared) from a Spector case. Use when given a Spector case link or a PR link that modifies Spector cases under http-specs\u002Fazure-http-specs.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpython-sdk-spector-mock-api-tests\u002FSKILL.md",[151,154,157,162],{"categoryNo":152,"categoryName":153,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":155,"categoryName":156,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":163,"categoryName":164,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000036","内容创作者",[166,32,115,167,168,118,169,99,170,171,172,38,20,35,27,173,174,175,101,24],"writing","writing python sdk spector mock api tests","api","writing python","mock","mock api","azure","shared","link","case",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":41},"01M69B79NV57JMNA7RS13MAE5P","pnpm-format","Format the codebase with pnpm and recover from common formatting failures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpnpm-format\u002FSKILL.md",[],[183,184,65,185,186,187,188],"pnpm format","format","common","formatting","with","codebase",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":41},"01M69B784PEAQ45ZKNZAX9NCA9","minimal-repro","Help create a minimal reproduction for a TypeSpec compiler or emitter bug. Use when a user provides TypeSpec source (pasted code or a GitHub URL) and describes an issue. Reproduces locally and reduces to a single-file repro.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fminimal-repro\u002FSKILL.md",[],[196,197,198,114,35,199,116,200,29,201,119,27,202,203,204,123,19,205,206,24],"minimal repro","repro","minimal","create","help","file","single-file","bug","issue","source","single"]