[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699BN3DWMBMS5QDBCPXASH6":3,"skill-same:01M699BN3DWMBMS5QDBCPXASH6":128},{"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":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M699BN3DWMBMS5QDBCPXASH6","write-changelog",null,"Write a CHANGELOG.md entry for a new extension release. Use when: writing changelog, updating changelog, adding release notes, preparing a release, documenting milestone changes. Requires a milestone name and extension version number.","microsoft\u002Fvscode-pull-request-github","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699BK74DGWQRPSMWS2B7HFZ",2641,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-changelog\u002FSKILL.md",[],[19,20,21],"write changelog","writing","github","2026-11-10 10:12:30",false,"---\nname: write-changelog\ndescription: 'Write a CHANGELOG.md entry for a new extension release. Use when: writing changelog, updating changelog, adding release notes, preparing a release, documenting milestone changes. Requires a milestone name and extension version number.'\nargument-hint: 'Provide the extension version (e.g. 0.134.0) and the GitHub milestone name (e.g. 1.112.0)'\n---\n\n# Write Changelog Entry\n\nGenerate a new entry in `CHANGELOG.md` for an extension release by gathering closed issues and merged PRs from a GitHub milestone.\n\n## Inputs\n\nThe user must provide:\n1. **Extension version number** - the version for the changelog heading (e.g. `0.134.0`)\n2. **GitHub milestone name** - the milestone to query (e.g. `1.112.0`)\n\n## Procedure\n\n### 1. Gather Milestone Items\n\nSearch for all closed items in the milestone scoped to `microsoft\u002Fvscode-pull-request-github`:\n\n- **Issues (bugs\u002Ffeatures):** Search for closed issues with `milestone:\"\u003Cname>\" repo:microsoft\u002Fvscode-pull-request-github is:closed`\n- **Merged PRs:** Search for merged PRs with `milestone:\"\u003Cname>\" repo:microsoft\u002Fvscode-pull-request-github is:pr is:merged`\n\n### 2. Classify Items\n\nSort every item into one of these buckets:\n\n| Bucket | Criteria |\n|--------|----------|\n| **Changes** | Feature requests, enhancements, new settings, new commands, infrastructure improvements (e.g. dependency upgrades, build system changes) |\n| **Fixes** | Items labeled `bug`, or PRs that fix a specific issue |\n| **Thank You** | Merged PRs authored by external contributors (user type is not `Bot`, and user is not a GitHub staff \u002F `site_admin`) |\n| **Skip** | Version-bump PRs (title is just a version like \"0.132.0\"), test plan items, items from other repos |\n\n### 3. Write the Entry\n\nInsert the new section **at the top** of `CHANGELOG.md`, directly after the `# Changelog` heading and before the previous release section.\n\nFollow this format exactly:\n\n```markdown\n## \u003Cversion>\n\n### Changes\n\n- Description of change one.\n- Description of change two with setting `\"settingName\"`.\n\n### Fixes\n\n- Short description of bug. https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fissues\u002F\u003Cnumber>\n- Another bug fix. https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fissues\u002F\u003Cnumber>\n\n**_Thank You_**\n\n* [@username (Display Name)](https:\u002F\u002Fgithub.com\u002Fusername): Short description of contribution [PR #1234](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fpull\u002F1234)\n```\n\n### Format Rules\n\n- **Changes:** Write a concise, user-facing description. Do NOT link to issues. Use backticks for setting names and commands. Each entry is a single `- ` bullet.\n- **Fixes:** Use the issue title (cleaned up for readability) followed by a space and the full issue URL. Each entry is a single `- ` bullet. If a fix came from a PR without a linked issue, describe it without a URL.\n- **Thank You:** Use `* ` bullets (not `- `). Format: `[@login (Name)](profile-url): Description [PR #number](pr-url)`. Only include for external community contributors.\n- **Sections:** Omit any section (`### Changes`, `### Fixes`, `**_Thank You_**`) if there are no items for it.\n- **No blank lines** between bullets within a section.\n- **One blank line** between sections.\n\n### 4. Validate\n\n- Confirm the new section is positioned correctly (after `# Changelog`, before the previous version).\n- Verify all issue\u002FPR links are correct and point to `microsoft\u002Fvscode-pull-request-github`.\n- Ensure no duplicate entries.\n","# Write Changelog Entry\n\nGenerate a new entry in `CHANGELOG.md` for an extension release by gathering closed issues and merged PRs from a GitHub milestone.\n\n## Inputs\n\nThe user must provide:\n1. **Extension version number** - the version for the changelog heading (e.g. `0.134.0`)\n2. **GitHub milestone name** - the milestone to query (e.g. `1.112.0`)\n\n## Procedure\n\n### 1. Gather Milestone Items\n\nSearch for all closed items in the milestone scoped to `microsoft\u002Fvscode-pull-request-github`:\n\n- **Issues (bugs\u002Ffeatures):** Search for closed issues with `milestone:\"\u003Cname>\" repo:microsoft\u002Fvscode-pull-request-github is:closed`\n- **Merged PRs:** Search for merged PRs with `milestone:\"\u003Cname>\" repo:microsoft\u002Fvscode-pull-request-github is:pr is:merged`\n\n### 2. Classify Items\n\nSort every item into one of these buckets:\n\n| Bucket | Criteria |\n|--------|----------|\n| **Changes** | Feature requests, enhancements, new settings, new commands, infrastructure improvements (e.g. dependency upgrades, build system changes) |\n| **Fixes** | Items labeled `bug`, or PRs that fix a specific issue |\n| **Thank You** | Merged PRs authored by external contributors (user type is not `Bot`, and user is not a GitHub staff \u002F `site_admin`) |\n| **Skip** | Version-bump PRs (title is just a version like \"0.132.0\"), test plan items, items from other repos |\n\n### 3. Write the Entry\n\nInsert the new section **at the top** of `CHANGELOG.md`, directly after the `# Changelog` heading and before the previous release section.\n\nFollow this format exactly:\n\n```markdown\n## \u003Cversion>\n\n### Changes\n\n- Description of change one.\n- Description of change two with setting `\"settingName\"`.\n\n### Fixes\n\n- Short description of bug. https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fissues\u002F\u003Cnumber>\n- Another bug fix. https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fissues\u002F\u003Cnumber>\n\n**_Thank You_**\n\n* [@username (Display Name)](https:\u002F\u002Fgithub.com\u002Fusername): Short description of contribution [PR #1234](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fpull\u002F1234)\n```\n\n### Format Rules\n\n- **Changes:** Write a concise, user-facing description. Do NOT link to issues. Use backticks for setting names and commands. Each entry is a single `- ` bullet.\n- **Fixes:** Use the issue title (cleaned up for readability) followed by a space and the full issue URL. Each entry is a single `- ` bullet. If a fix came from a PR without a linked issue, describe it without a URL.\n- **Thank You:** Use `* ` bullets (not `- `). Format: `[@login (Name)](profile-url): Description [PR #number](pr-url)`. Only include for external community contributors.\n- **Sections:** Omit any section (`### Changes`, `### Fixes`, `**_Thank You_**`) if there are no items for it.\n- **No blank lines** between bullets within a section.\n- **One blank line** between sections.\n\n### 4. Validate\n\n- Confirm the new section is positioned correctly (after `# Changelog`, before the previous version).\n- Verify all issue\u002FPR links are correct and point to `microsoft\u002Fvscode-pull-request-github`.\n- Ensure no duplicate entries.\n",{"name":5,"description":7,"argument-hint":27},"Provide the extension version (e.g. 0.134.0) and the GitHub milestone name (e.g. 1.112.0)","main","34775cfc87d977c5562f7bbf7771878e8ab00470",".github\u002Fskills\u002Fwrite-changelog",817,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github","https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=GitHub.vscode-pull-request-github","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-11 00:18:24",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add microsoft\u002Fvscode-pull-request-github --skill write-changelog",{"tool":44,"command":45},"bunx","bunx skills add microsoft\u002Fvscode-pull-request-github --skill write-changelog",{"tool":47,"command":48},"pnpm","pnpm dlx skills add microsoft\u002Fvscode-pull-request-github --skill write-changelog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-changelog\u002FSKILL.md",true,[52,58,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"data\u002Fdomain-complexity.csv","ASSET","资产文件",7324,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fdata\u002Fdomain-complexity.csv",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"data\u002Fprd-purpose.md","REFERENCE","参考文档",7246,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fdata\u002Fprd-purpose.md",{"path":65,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":66,"sourceHtmlUrl":67},"data\u002Fproject-types.csv",3144,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fdata\u002Fproject-types.csv",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"steps-v\u002Fstep-v-01-discovery.md",7177,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-01-discovery.md",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"steps-v\u002Fstep-v-02-format-detection.md",6507,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-02-format-detection.md",{"path":77,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":78,"sourceHtmlUrl":79},"steps-v\u002Fstep-v-02b-parity-check.md",6419,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-02b-parity-check.md",{"path":81,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":82,"sourceHtmlUrl":83},"steps-v\u002Fstep-v-03-density-validation.md",5755,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-03-density-validation.md",{"path":85,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":86,"sourceHtmlUrl":87},"steps-v\u002Fstep-v-04-brief-coverage-validation.md",7189,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-04-brief-coverage-validation.md",{"path":89,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":90,"sourceHtmlUrl":91},"steps-v\u002Fstep-v-05-measurability-validation.md",7109,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-05-measurability-validation.md",{"path":93,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":94,"sourceHtmlUrl":95},"steps-v\u002Fstep-v-06-traceability-validation.md",7238,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-06-traceability-validation.md",{"path":97,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":98,"sourceHtmlUrl":99},"steps-v\u002Fstep-v-07-implementation-leakage-validation.md",7005,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-07-implementation-leakage-validation.md",{"path":101,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":102,"sourceHtmlUrl":103},"steps-v\u002Fstep-v-08-domain-compliance-validation.md",7691,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-08-domain-compliance-validation.md",{"path":105,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":106,"sourceHtmlUrl":107},"steps-v\u002Fstep-v-09-project-type-validation.md",8603,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-09-project-type-validation.md",{"path":109,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":110,"sourceHtmlUrl":111},"steps-v\u002Fstep-v-10-smart-validation.md",6785,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-10-smart-validation.md",{"path":113,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":114,"sourceHtmlUrl":115},"steps-v\u002Fstep-v-11-holistic-quality-validation.md",8736,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-11-holistic-quality-validation.md",{"path":117,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":118,"sourceHtmlUrl":119},"steps-v\u002Fstep-v-12-completeness-validation.md",8233,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-12-completeness-validation.md",{"path":121,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":122,"sourceHtmlUrl":123},"steps-v\u002Fstep-v-13-report-complete.md",8134,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fsteps-v\u002Fstep-v-13-report-complete.md",{"path":125,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":126,"sourceHtmlUrl":127},"workflow.md",2918,"https:\u002F\u002Fgithub.com\u002Fsherryswift1019-gif\u002FAI-DZHT\u002Fblob\u002Fmain\u002F_bmad\u002Fbmm\u002F2-plan-workflows\u002Fbmad-validate-prd\u002Fworkflow.md",[129,146,154,162,171,181],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":143,"publishedAt":22},"01M699BZZ0CARTV3XNQ1TREA1E","summarize-github-issue-pr-notification","Summarizes the content of a GitHub issue, pull request (PR), or notification, providing a concise overview of the main points and key details. ALWAYS use the skill when asked to summarize an issue, PR, or notification.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fblob\u002Fmain\u002Fsrc\u002Flm\u002Fskills\u002Fsummarize-github-issue-pr-notification\u002FSKILL.md",[135,140],{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":141,"categoryName":142,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000021","资料检索与研究",[144,21,145],"summarize","summarize github issue pr notification",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":22},"01M699BY85Z5RDVKENPYAJ0CA9","suggest-fix-issue","Given the details of an issue, suggests a fix for the issue.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fblob\u002Fmain\u002Fsrc\u002Flm\u002Fskills\u002Fsuggest-fix-issue\u002FSKILL.md",[],[153],"suggest fix issue",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":22},"01M699BWKADDDEV288A6J871TA","show-github-search-result","Summarizes the results of a GitHub search query in a human friendly markdown table that is easy to read and understand. ALWAYS use this skill when displaying the results of a GitHub search query.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fblob\u002Fmain\u002Fsrc\u002Flm\u002Fskills\u002Fshow-github-search-result\u002FSKILL.md",[],[21,161],"show github search result",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":22},"01M699BTGCY8GANZTV8CC6RH91","form-github-search-query","Forms a GitHub search query based on a natural language query and the type of search (issue or PR). This skill helps users create effective search queries to find relevant issues or pull requests on GitHub.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fblob\u002Fmain\u002Fsrc\u002Flm\u002Fskills\u002Fform-github-search-query\u002FSKILL.md",[],[21,169,170],"form github search query","pull requests",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":22},"01M699BRWP3CH27AN77HK412C4","create-pull-request","Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fblob\u002Fmain\u002Fsrc\u002Flm\u002Fskills\u002Fcreate-pull-request\u002FSKILL.md",[177],{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},[179,180,21],"create pull request","review",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"publishedAt":22},"01M699BQ161D5WPGV0DBBQW02C","address-pr-comments","Address review comments (including Copilot comments) on the active pull request. Use when: responding to PR feedback, fixing review comments, resolving PR threads, implementing requested changes from reviewers, addressing code review, fixing PR issues.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-pull-request-github\u002Fblob\u002Fmain\u002Fsrc\u002Flm\u002Fskills\u002Faddress-pr-comments\u002FSKILL.md",[187],{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},[189,190,180],"address pr comments","code review"]