[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69B76464N72EBS07HC4NMWJ":3,"skill-same:01M69B76464N72EBS07HC4NMWJ":66},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M69B76464N72EBS07HC4NMWJ","http-client-python-bump-and-release",null,"Create a PR to bump TypeSpec\u002FAzure Tools dependencies, update peer dependencies, or release a new version of the http-client-python package.","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\u002Fhttp-client-python-bump-and-release\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"http","http client","client","http client python bump and release","release","python","bump","package","new","dependencies","peer","version","Tools","update","create","typespec","pr","azure","2026-11-10 10:12:30",false,"---\nname: http-client-python-bump-and-release\ndescription: Create a PR to bump TypeSpec\u002FAzure Tools dependencies, update peer dependencies, or release a new version of the http-client-python package.\n---\n\n# HTTP Client Python Bump and Release\n\nCreate a PR to bump dependencies and release a new version of the http-client-python package.\n\n> **Note:** `{REPO}` refers to the root folder of the `microsoft\u002Ftypespec` repository.\n\n## Prerequisites\n\nBefore starting, verify that `npm-check-updates` is available:\n\n```bash\nnpx --no-install npm-check-updates --version\n```\n\nIf the command fails or prompts for installation, install it globally:\n\n```bash\nnpm install -g npm-check-updates\n```\n\nThe version script also requires pnpm and the repository's workspace dependencies, even though the emitter uses npm. Verify that `pnpm --version` and `pnpm exec chronus --version` work from `{REPO}`. If pnpm is missing, install the version declared in the root `package.json`'s `packageManager` field. If Chronus is missing, run `pnpm install --frozen-lockfile` from `{REPO}` before continuing.\n\nUse the CFS feed `https:\u002F\u002Fpkgs.dev.azure.com\u002Fazure-sdk\u002Fpublic\u002F_packaging\u002Fazure-sdk-for-js\u002Fnpm\u002Fregistry\u002F` for dependency queries and installation. From the package directory, verify that `npm config get registry` reports this feed; it is configured in the package's `.npmrc`. Do not silently fall back to npmjs.org if the feed is unavailable.\n\n## Workflow\n\n1. Navigate to the package directory:\n\n   ```bash\n   cd {REPO}\u002Fpackages\u002Fhttp-client-python\n   ```\n\n2. Inspect the worktree and fetch main without discarding local changes:\n\n   ```bash\n   git status --short\n   git fetch origin main\n   ```\n\n   Preserve unrelated local work. Do not run `git reset` or `git checkout .` as release preparation.\n\n3. Create release branch (use current date in MM-DD format):\n\n   ```bash\n   git switch -c publish\u002Fpython-release-{MM-DD} origin\u002Fmain\n   ```\n\n4. Update dependencies:\n\n   ```bash\n   npx npm-check-updates -u --filter '@typespec\u002F*,@azure-tools\u002F*' --packageFile package.json --registry https:\u002F\u002Fpkgs.dev.azure.com\u002Fazure-sdk\u002Fpublic\u002F_packaging\u002Fazure-sdk-for-js\u002Fnpm\u002Fregistry\u002F\n   ```\n\n5. Update `peerDependencies` in package.json:\n   - Do not assume step 4 updated peer dependencies: in the release run it updated development dependencies but left peer lower bounds unchanged. Use the latest versions reported in step 4 for the corresponding peers.\n   - If format is `\">=0.a.b \u003C1.0.0\"`: Update only the `0.a.b` portion, keep the range format unchanged\n   - If format is `\"^1.a.b\"`: Update to the latest version\n\n6. Verify `devDependencies` versions for specs:\n   - Check `@typespec\u002Fhttp-specs` and `@azure-tools\u002Fazure-http-specs`\n   - If the original version in `package.json` is newer than the updated value, keep the original version\n   - Dev versions are typically in the form `x.y.z-alpha.N-dev.M` (e.g., `0.1.0-alpha.37-dev.3`).\n\n   Example:\n   - Original: `@typespec\u002Fhttp-specs: 0.1.0-alpha.12-dev.5`, updated by step 4 to `0.1.0-alpha.11` → keep `0.1.0-alpha.12-dev.5`.\n   - Original: `@typespec\u002Fhttp-specs: 0.1.0-alpha.12-dev.5`, updated by step 4 to `0.1.0-alpha.12` → keep `0.1.0-alpha.12` (step 4 works as expected).\n   - Original: `@azure-tools\u002Fazure-http-specs: 0.1.0-alpha.12-dev.2`, updated to `0.1.0-alpha.11` → keep `0.1.0-alpha.12-dev.2`.\n   - Original: `@azure-tools\u002Fazure-http-specs: 0.1.0-alpha.12-dev.2`, updated to `0.1.0-alpha.12` → keep `0.1.0-alpha.12` (step 4 works as expected).\n\n7. Run version change script:\n\n   ```bash\n   npm run change:version\n   ```\n\n   Verify that the script updated both the emitter version in `package.json` and `CHANGELOG.md`. If neither file was updated:\n   - Increment the third component of the emitter version in `package.json` (for example, `a.b.c` to `a.b.(c+1)`).\n   - Add this entry near the top of `CHANGELOG.md`, immediately after the changelog title:\n\n     ```markdown\n     ## \u003Cnew emitter version>\n\n     ### Bump dependencies\n\n     - Bump dependencies of `@typespec\u002F*` and `@azure-tools\u002F*` to latest versions\n     ```\n\n   Verify that the version in `package.json` matches the new `CHANGELOG.md` heading. Consumed Python change files under `.chronus\u002Fchanges\u002F` are expected deletions; include them in the release commit.\n\n8. Install, build, validate, and commit:\n\n   ```bash\n   npm install --registry=https:\u002F\u002Fpkgs.dev.azure.com\u002Fazure-sdk\u002Fpublic\u002F_packaging\u002Fazure-sdk-for-js\u002Fnpm\u002Fregistry\u002F && npm run build\n   npm run lint\n   npm run test:emitter\n   ```\n\n   Run formatting from `{REPO}` using the `pnpm-format` skill. If `packages\u002Fprettier-plugin-typespec\u002Fdist\u002Findex.js` is missing, build the formatter first with `pnpm -r --filter '@typespec\u002Fprettier-plugin-typespec...' build`, then run `pnpm format`. Do not repeat dependency installation or build the entire monorepo for this missing-plugin error.\n\n   Verify that `package-lock.json` and its root package entry match the manifest version, peer dependencies, and development dependencies. Review `git diff --check` and the changed-file list; stage only the release manifest, lockfile, changelog, and consumed Python change files. Commit using a conventional message such as `chore(python): bump version to \u003Cversion>` and the required co-author trailer.\n\n   Check the lockfile diff for registry changes: preserve existing CFS URLs and resolve new or updated packages through CFS, without migrating unrelated pre-existing npmjs.org entries. Changing the registry and rerunning `npm install --package-lock-only` did not repair existing npmjs.org URLs in the release run. If correcting such a lockfile, obtain the exact CFS tarball URLs from feed metadata and verify their contents against the lockfile integrity hashes before replacing URLs; do not blindly rewrite hosts or change package versions.\n\n9. Push and create PR:\n\n   ```bash\n   cd {REPO}\n   git push origin HEAD\n   ```\n\n10. Create PR with title `[python] release new version` and no description.\n\n    Verify the created PR's title, description, base\u002Fhead branches, and draft state rather than relying on the creation tool's output. The release run's PR tool inserted a placeholder despite receiving an empty body; if this happens, clear it with `gh api --method PATCH repos\u002Fmicrosoft\u002Ftypespec\u002Fpulls\u002F\u003Cnumber> -f body=''` and verify again. If the tool creates a draft, mark it ready with `gh pr ready \u003Cnumber>` unless the user requested a draft.\n\n## Post-Process Review\n\n1. After the pull request is created, review the complete release run: commands executed, command output, manual interventions, validation results, changed files, commit, push, cleanup, and PR creation.\n2. Update this skill only when the completed run provides a concrete finding and a strong reason for the change, such as:\n   - A documented step failed or produced an incorrect result.\n   - The agent needed an undocumented manual correction to complete the release.\n   - A step was ambiguous enough to create a real risk or delay.\n   - A command was unnecessary or could be replaced by a demonstrably safer or more reliable command.\n3. Do not change the skill based on preference, speculation, or an unobserved edge case. For every update, record the observed evidence and explain why the edit improves future releases.\n4. Keep any skill update minimal, validate its formatting and frontmatter, and keep it separate from the completed release PR unless the user explicitly asks to include it there.\n5. If the review finds no evidence-backed improvement, leave the skill unchanged and state that no update was warranted.\n6. Return the branch name, prepared `@typespec\u002Fhttp-client-python` version, commit hash, pull request URL, review findings, and any skill update to the user. Creating a release PR does not mean the package has been published.\n","# HTTP Client Python Bump and Release\n\nCreate a PR to bump dependencies and release a new version of the http-client-python package.\n\n> **Note:** `{REPO}` refers to the root folder of the `microsoft\u002Ftypespec` repository.\n\n## Prerequisites\n\nBefore starting, verify that `npm-check-updates` is available:\n\n```bash\nnpx --no-install npm-check-updates --version\n```\n\nIf the command fails or prompts for installation, install it globally:\n\n```bash\nnpm install -g npm-check-updates\n```\n\nThe version script also requires pnpm and the repository's workspace dependencies, even though the emitter uses npm. Verify that `pnpm --version` and `pnpm exec chronus --version` work from `{REPO}`. If pnpm is missing, install the version declared in the root `package.json`'s `packageManager` field. If Chronus is missing, run `pnpm install --frozen-lockfile` from `{REPO}` before continuing.\n\nUse the CFS feed `https:\u002F\u002Fpkgs.dev.azure.com\u002Fazure-sdk\u002Fpublic\u002F_packaging\u002Fazure-sdk-for-js\u002Fnpm\u002Fregistry\u002F` for dependency queries and installation. From the package directory, verify that `npm config get registry` reports this feed; it is configured in the package's `.npmrc`. Do not silently fall back to npmjs.org if the feed is unavailable.\n\n## Workflow\n\n1. Navigate to the package directory:\n\n   ```bash\n   cd {REPO}\u002Fpackages\u002Fhttp-client-python\n   ```\n\n2. Inspect the worktree and fetch main without discarding local changes:\n\n   ```bash\n   git status --short\n   git fetch origin main\n   ```\n\n   Preserve unrelated local work. Do not run `git reset` or `git checkout .` as release preparation.\n\n3. Create release branch (use current date in MM-DD format):\n\n   ```bash\n   git switch -c publish\u002Fpython-release-{MM-DD} origin\u002Fmain\n   ```\n\n4. Update dependencies:\n\n   ```bash\n   npx npm-check-updates -u --filter '@typespec\u002F*,@azure-tools\u002F*' --packageFile package.json --registry https:\u002F\u002Fpkgs.dev.azure.com\u002Fazure-sdk\u002Fpublic\u002F_packaging\u002Fazure-sdk-for-js\u002Fnpm\u002Fregistry\u002F\n   ```\n\n5. Update `peerDependencies` in package.json:\n   - Do not assume step 4 updated peer dependencies: in the release run it updated development dependencies but left peer lower bounds unchanged. Use the latest versions reported in step 4 for the corresponding peers.\n   - If format is `\">=0.a.b \u003C1.0.0\"`: Update only the `0.a.b` portion, keep the range format unchanged\n   - If format is `\"^1.a.b\"`: Update to the latest version\n\n6. Verify `devDependencies` versions for specs:\n   - Check `@typespec\u002Fhttp-specs` and `@azure-tools\u002Fazure-http-specs`\n   - If the original version in `package.json` is newer than the updated value, keep the original version\n   - Dev versions are typically in the form `x.y.z-alpha.N-dev.M` (e.g., `0.1.0-alpha.37-dev.3`).\n\n   Example:\n   - Original: `@typespec\u002Fhttp-specs: 0.1.0-alpha.12-dev.5`, updated by step 4 to `0.1.0-alpha.11` → keep `0.1.0-alpha.12-dev.5`.\n   - Original: `@typespec\u002Fhttp-specs: 0.1.0-alpha.12-dev.5`, updated by step 4 to `0.1.0-alpha.12` → keep `0.1.0-alpha.12` (step 4 works as expected).\n   - Original: `@azure-tools\u002Fazure-http-specs: 0.1.0-alpha.12-dev.2`, updated to `0.1.0-alpha.11` → keep `0.1.0-alpha.12-dev.2`.\n   - Original: `@azure-tools\u002Fazure-http-specs: 0.1.0-alpha.12-dev.2`, updated to `0.1.0-alpha.12` → keep `0.1.0-alpha.12` (step 4 works as expected).\n\n7. Run version change script:\n\n   ```bash\n   npm run change:version\n   ```\n\n   Verify that the script updated both the emitter version in `package.json` and `CHANGELOG.md`. If neither file was updated:\n   - Increment the third component of the emitter version in `package.json` (for example, `a.b.c` to `a.b.(c+1)`).\n   - Add this entry near the top of `CHANGELOG.md`, immediately after the changelog title:\n\n     ```markdown\n     ## \u003Cnew emitter version>\n\n     ### Bump dependencies\n\n     - Bump dependencies of `@typespec\u002F*` and `@azure-tools\u002F*` to latest versions\n     ```\n\n   Verify that the version in `package.json` matches the new `CHANGELOG.md` heading. Consumed Python change files under `.chronus\u002Fchanges\u002F` are expected deletions; include them in the release commit.\n\n8. Install, build, validate, and commit:\n\n   ```bash\n   npm install --registry=https:\u002F\u002Fpkgs.dev.azure.com\u002Fazure-sdk\u002Fpublic\u002F_packaging\u002Fazure-sdk-for-js\u002Fnpm\u002Fregistry\u002F && npm run build\n   npm run lint\n   npm run test:emitter\n   ```\n\n   Run formatting from `{REPO}` using the `pnpm-format` skill. If `packages\u002Fprettier-plugin-typespec\u002Fdist\u002Findex.js` is missing, build the formatter first with `pnpm -r --filter '@typespec\u002Fprettier-plugin-typespec...' build`, then run `pnpm format`. Do not repeat dependency installation or build the entire monorepo for this missing-plugin error.\n\n   Verify that `package-lock.json` and its root package entry match the manifest version, peer dependencies, and development dependencies. Review `git diff --check` and the changed-file list; stage only the release manifest, lockfile, changelog, and consumed Python change files. Commit using a conventional message such as `chore(python): bump version to \u003Cversion>` and the required co-author trailer.\n\n   Check the lockfile diff for registry changes: preserve existing CFS URLs and resolve new or updated packages through CFS, without migrating unrelated pre-existing npmjs.org entries. Changing the registry and rerunning `npm install --package-lock-only` did not repair existing npmjs.org URLs in the release run. If correcting such a lockfile, obtain the exact CFS tarball URLs from feed metadata and verify their contents against the lockfile integrity hashes before replacing URLs; do not blindly rewrite hosts or change package versions.\n\n9. Push and create PR:\n\n   ```bash\n   cd {REPO}\n   git push origin HEAD\n   ```\n\n10. Create PR with title `[python] release new version` and no description.\n\n    Verify the created PR's title, description, base\u002Fhead branches, and draft state rather than relying on the creation tool's output. The release run's PR tool inserted a placeholder despite receiving an empty body; if this happens, clear it with `gh api --method PATCH repos\u002Fmicrosoft\u002Ftypespec\u002Fpulls\u002F\u003Cnumber> -f body=''` and verify again. If the tool creates a draft, mark it ready with `gh pr ready \u003Cnumber>` unless the user requested a draft.\n\n## Post-Process Review\n\n1. After the pull request is created, review the complete release run: commands executed, command output, manual interventions, validation results, changed files, commit, push, cleanup, and PR creation.\n2. Update this skill only when the completed run provides a concrete finding and a strong reason for the change, such as:\n   - A documented step failed or produced an incorrect result.\n   - The agent needed an undocumented manual correction to complete the release.\n   - A step was ambiguous enough to create a real risk or delay.\n   - A command was unnecessary or could be replaced by a demonstrably safer or more reliable command.\n3. Do not change the skill based on preference, speculation, or an unobserved edge case. For every update, record the observed evidence and explain why the edit improves future releases.\n4. Keep any skill update minimal, validate its formatting and frontmatter, and keep it separate from the completed release PR unless the user explicitly asks to include it there.\n5. If the review finds no evidence-backed improvement, leave the skill unchanged and state that no update was warranted.\n6. Return the branch name, prepared `@typespec\u002Fhttp-client-python` version, commit hash, pull request URL, review findings, and any skill update to the user. Creating a release PR does not mean the package has been published.\n",{"name":5,"description":7},"main","3a87c089009146e1ce1201659c00f1179411a81f",".github\u002Fskills\u002Fhttp-client-python-bump-and-release",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add microsoft\u002Ftypespec --skill http-client-python-bump-and-release",{"tool":58,"command":59},"bunx","bunx skills add microsoft\u002Ftypespec --skill http-client-python-bump-and-release",{"tool":61,"command":62},"pnpm","pnpm dlx skills add microsoft\u002Ftypespec --skill http-client-python-bump-and-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftypespec\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fhttp-client-python-bump-and-release\u002FSKILL.md",true,[],[67,100,123,144,174,187],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":81,"publishedAt":37},"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",[73,78],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":79,"categoryName":80,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000023","Skill与智能体开发",[82,83,84,24,85,86,87,19,34,88,26,89,90,91,92,93,94,95,96,97,98,99],"test","test unbranded emitter","testing","build and test","validate","run tests","run","ci","check","fix","use","test suite","build","local","tests","triggers","generator","changes",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":37},"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",[106],{"categoryNo":79,"categoryName":80,"taxonomyType":76,"taxonomyTypeDesc":77},[34,108,109,110,24,111,112,113,114,115,116,92,117,95,118,21,119,120,121,122],"generate from typespec","generate","spec","github","sdk","code","compile","python sdk","user","specification","project","URL","for","things","when",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":37},"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",[129],{"categoryNo":79,"categoryName":80,"taxonomyType":76,"taxonomyTypeDesc":77},[131,132,133,24,86,113,134,135,136,137,138,92,139,140,95,141,142,121,99,143,122],"diff upstream","diff","upstream","produce","baseline","show me","how","generated","show","me","compare","output","expected",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":164,"publishedAt":37},"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",[150,153,156,161],{"categoryNo":151,"categoryName":152,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":154,"categoryName":155,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":157,"categoryName":158,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":162,"categoryName":163,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000036","内容创作者",[165,24,112,166,167,115,168,96,169,170,36,19,35,34,92,171,172,173,98,122],"writing","writing python sdk spector mock api tests","api","writing python","mock","mock api","shared","link","case",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":37},"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",[],[181,182,61,183,184,185,186],"pnpm format","format","common","formatting","with","codebase",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":37},"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",[],[194,195,196,111,34,33,113,197,198,199,116,92,200,201,202,119,120,203,204,122],"minimal repro","repro","minimal","help","compiler","file","single-file","bug","issue","source","single"]