[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699B0ADBE2892F6W4NJ5TZW":3,"skill-same:01M699B0ADBE2892F6W4NJ5TZW":81},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M699B0ADBE2892F6W4NJ5TZW","pull-requests",null,"Guidance for creating pull requests and handling PR review comments in the Agent Framework repository. Use this when writing a PR description (filling out the PR template) or when responding to and resolving review comments on an existing PR.","microsoft\u002Fagent-framework","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6999R99RF2DY8AXYFS5HZRM",14676,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fpython\u002F.github\u002Fskills\u002Fpull-requests\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"pull requests","requests","pull","repository","when","Existing","for","comments","guidance","use","creating pull requests","template","writing","framework","pr description","pr","pr review","pr review comments","agent framework","review","2026-11-10 10:12:30",false,"---\nname: pull-requests\ndescription: >\n  Guidance for creating pull requests and handling PR review comments in the\n  Agent Framework repository. Use this when writing a PR description (filling out\n  the PR template) or when responding to and resolving review comments on an\n  existing PR.\n---\n\n# Pull Request Workflow\n\nThis skill covers two tasks: (1) writing a high-quality PR description, and\n(2) handling review comments on an existing PR.\n\n## 1. Writing the PR description\n\nAlways follow the repository PR template at\n[`.github\u002Fpull_request_template.md`](..\u002F..\u002F..\u002F..\u002F.github\u002Fpull_request_template.md). Keep its\nexact structure and headings. Fill every section:\n\n### `### Motivation & Context`\nExplain *why* the change is needed: the problem it solves and the scenario it\ncontributes to. Describe the net change relative to `main` — this is implied, so\ndo **not** spell out \"vs main\" explicitly.\n\n### `### Description & Review Guide`\nDescribe the changes, the overall approach, and the design. Answer the three\nprompts:\n- **What are the major changes?**\n- **What is the impact of these changes?**\n- **What do you want reviewers to focus on?** — This item is for **human\n  reviewers only**. Automated\u002FAI reviewers must ignore it and review the entire\n  change rather than narrowing scope to it.\n\nFor material Python public-API changes, follow the additional guidance in the\n[root PR skill's Description & Review Guide section](..\u002F..\u002F..\u002F..\u002F.github\u002Fskills\u002Fpull-requests\u002FSKILL.md#-description--review-guide).\n\n### `### Related Issue`\nLink the issue the PR fixes using a GitHub closing keyword (`Fixes #123` \u002F\n`Closes #123`) so it closes automatically on merge. For a non-trivial change,\nconfirm that a maintainer added the `ready-for-implementation` label or explicitly\nagreed with the direction in an issue comment. A PR with no agreed issue may be\nclosed without detailed review. Before opening, confirm there is no other open PR\nfor the same issue; if there is, explain how this PR differs.\n\nFor team-only work and investigation or planning outcomes, follow the approval\nboundaries in the [root PR skill's Related Issue section](..\u002F..\u002F..\u002F..\u002F.github\u002Fskills\u002Fpull-requests\u002FSKILL.md#-related-issue).\n\nFor a trivial change that does not require an issue, replace the `Fixes #`\nplaceholder with `N\u002FA - trivial change` and briefly explain why the change is an\nobvious correction whose desired result is not reasonably in dispute.\n\nFor repository-maintained scheduled automation, replace the placeholder with\n`N\u002FA - repository automation` and identify the generating workflow.\n\n### `### AI Assistance`\nCheck exactly one option:\n- Select **\"No material AI assistance was used.\"** only when generative AI did\n  not create or substantially transform submitted content.\n- Otherwise select **\"This is an AI-assisted contribution.\"** and briefly\n  identify the assisted areas.\n\nGenerating or substantially editing the PR description with Copilot counts as\nmaterial AI assistance even if the implementation itself was not AI-assisted.\nNever include prompts or sensitive information in the disclosure.\n\n### `### Contribution Checklist`\nCheck every item that applies. Confirm that the PR links to an agreed issue or\ndocuments a trivial-change or repository-automation exception. For the\nbreaking-change item:\n- Leave **\"This is not a breaking change.\"** checked for the common case.\n- If the change **is** breaking, add the `breaking change` label **or** put\n  `[BREAKING]` in the title prefix, before or after a language prefix such as\n  `Python:` or `.NET:` — workflows keep the label and the title prefix in sync\n  automatically (see `.github\u002Fworkflows\u002Flabel-title-prefix.yml` and\n  `.github\u002Fworkflows\u002Flabel-pr.yml`).\n\n### Do not\n- Do **not** add ad-hoc sections such as \"Validation\" or \"Tests run\"; CI\u002FCD and\n  the checklist already cover validation status.\n- Do **not** remove or reorder the template's headings.\n\n### Creating the PR\nOpen new PRs as **drafts** until they are ready for review. Example:\n\n```bash\ngh pr create --repo microsoft\u002Fagent-framework --base main \\\n  --head \u003Cyour-fork-owner>:\u003Cbranch> --draft \\\n  --title \"\u003Cconcise title>\" --body \"\u003Cbody following the template>\"\n```\n\n## 2. Handling review comments\n\nWhen a PR receives review comments, follow this sequence — **do not start editing\ncode before the user has reviewed the plan**:\n\n1. **Review the comments.** Read every review comment and thread on the PR,\n   including inline code comments and general review summaries.\n2. **Make a plan.** Produce a concrete plan describing how each comment will be\n   addressed (or why it should not be, with reasoning).\n3. **Let the user review the plan.** Present the plan and wait for the user's\n   approval or adjustments before implementing anything.\n4. **Implement.** Make the agreed changes.\n5. **Reply to every comment.** Add a reply to **all** comments explaining how it\n   was addressed, preferably citing the commit containing the change. If the\n   feedback was not addressed, explain why. Leave no comment unanswered.\n6. **Resolve completed threads yourself.** After replying and completing any\n   necessary discussion, resolve the review thread. Do not wait for the reviewer\n   or a maintainer to resolve it. Leave a thread open only while it has an\n   unanswered question or active discussion.\n\n### Useful commands\n\nList review comments and threads:\n\n```bash\n# Inline review comments\ngh api repos\u002F{owner}\u002F{repo}\u002Fpulls\u002F{pr}\u002Fcomments\n\n# Review threads with resolution state (GraphQL)\ngh api graphql -f query='\n  query($owner:String!,$repo:String!,$pr:Int!){\n    repository(owner:$owner,name:$repo){\n      pullRequest(number:$pr){\n        reviewThreads(first:100){\n          nodes{ id isResolved comments(first:50){ nodes{ id body author{login} } } }\n        }\n      }\n    }\n  }' -F owner={owner} -F repo={repo} -F pr={pr}\n```\n\nReply to an inline review comment:\n\n```bash\ngh api repos\u002F{owner}\u002F{repo}\u002Fpulls\u002F{pr}\u002Fcomments\u002F{comment_id}\u002Freplies \\\n  -f body=\"Addressed in \u003Ccommit>: \u003Cexplanation>\"\n```\n\nResolve a review thread (needs the thread node id from the GraphQL query above):\n\n```bash\ngh api graphql -f query='\n  mutation($threadId:ID!){\n    resolveReviewThread(input:{threadId:$threadId}){ thread{ isResolved } }\n  }' -F threadId={thread_id}\n```\n","# Pull Request Workflow\n\nThis skill covers two tasks: (1) writing a high-quality PR description, and\n(2) handling review comments on an existing PR.\n\n## 1. Writing the PR description\n\nAlways follow the repository PR template at\n[`.github\u002Fpull_request_template.md`](..\u002F..\u002F..\u002F..\u002F.github\u002Fpull_request_template.md). Keep its\nexact structure and headings. Fill every section:\n\n### `### Motivation & Context`\nExplain *why* the change is needed: the problem it solves and the scenario it\ncontributes to. Describe the net change relative to `main` — this is implied, so\ndo **not** spell out \"vs main\" explicitly.\n\n### `### Description & Review Guide`\nDescribe the changes, the overall approach, and the design. Answer the three\nprompts:\n- **What are the major changes?**\n- **What is the impact of these changes?**\n- **What do you want reviewers to focus on?** — This item is for **human\n  reviewers only**. Automated\u002FAI reviewers must ignore it and review the entire\n  change rather than narrowing scope to it.\n\nFor material Python public-API changes, follow the additional guidance in the\n[root PR skill's Description & Review Guide section](..\u002F..\u002F..\u002F..\u002F.github\u002Fskills\u002Fpull-requests\u002FSKILL.md#-description--review-guide).\n\n### `### Related Issue`\nLink the issue the PR fixes using a GitHub closing keyword (`Fixes #123` \u002F\n`Closes #123`) so it closes automatically on merge. For a non-trivial change,\nconfirm that a maintainer added the `ready-for-implementation` label or explicitly\nagreed with the direction in an issue comment. A PR with no agreed issue may be\nclosed without detailed review. Before opening, confirm there is no other open PR\nfor the same issue; if there is, explain how this PR differs.\n\nFor team-only work and investigation or planning outcomes, follow the approval\nboundaries in the [root PR skill's Related Issue section](..\u002F..\u002F..\u002F..\u002F.github\u002Fskills\u002Fpull-requests\u002FSKILL.md#-related-issue).\n\nFor a trivial change that does not require an issue, replace the `Fixes #`\nplaceholder with `N\u002FA - trivial change` and briefly explain why the change is an\nobvious correction whose desired result is not reasonably in dispute.\n\nFor repository-maintained scheduled automation, replace the placeholder with\n`N\u002FA - repository automation` and identify the generating workflow.\n\n### `### AI Assistance`\nCheck exactly one option:\n- Select **\"No material AI assistance was used.\"** only when generative AI did\n  not create or substantially transform submitted content.\n- Otherwise select **\"This is an AI-assisted contribution.\"** and briefly\n  identify the assisted areas.\n\nGenerating or substantially editing the PR description with Copilot counts as\nmaterial AI assistance even if the implementation itself was not AI-assisted.\nNever include prompts or sensitive information in the disclosure.\n\n### `### Contribution Checklist`\nCheck every item that applies. Confirm that the PR links to an agreed issue or\ndocuments a trivial-change or repository-automation exception. For the\nbreaking-change item:\n- Leave **\"This is not a breaking change.\"** checked for the common case.\n- If the change **is** breaking, add the `breaking change` label **or** put\n  `[BREAKING]` in the title prefix, before or after a language prefix such as\n  `Python:` or `.NET:` — workflows keep the label and the title prefix in sync\n  automatically (see `.github\u002Fworkflows\u002Flabel-title-prefix.yml` and\n  `.github\u002Fworkflows\u002Flabel-pr.yml`).\n\n### Do not\n- Do **not** add ad-hoc sections such as \"Validation\" or \"Tests run\"; CI\u002FCD and\n  the checklist already cover validation status.\n- Do **not** remove or reorder the template's headings.\n\n### Creating the PR\nOpen new PRs as **drafts** until they are ready for review. Example:\n\n```bash\ngh pr create --repo microsoft\u002Fagent-framework --base main \\\n  --head \u003Cyour-fork-owner>:\u003Cbranch> --draft \\\n  --title \"\u003Cconcise title>\" --body \"\u003Cbody following the template>\"\n```\n\n## 2. Handling review comments\n\nWhen a PR receives review comments, follow this sequence — **do not start editing\ncode before the user has reviewed the plan**:\n\n1. **Review the comments.** Read every review comment and thread on the PR,\n   including inline code comments and general review summaries.\n2. **Make a plan.** Produce a concrete plan describing how each comment will be\n   addressed (or why it should not be, with reasoning).\n3. **Let the user review the plan.** Present the plan and wait for the user's\n   approval or adjustments before implementing anything.\n4. **Implement.** Make the agreed changes.\n5. **Reply to every comment.** Add a reply to **all** comments explaining how it\n   was addressed, preferably citing the commit containing the change. If the\n   feedback was not addressed, explain why. Leave no comment unanswered.\n6. **Resolve completed threads yourself.** After replying and completing any\n   necessary discussion, resolve the review thread. Do not wait for the reviewer\n   or a maintainer to resolve it. Leave a thread open only while it has an\n   unanswered question or active discussion.\n\n### Useful commands\n\nList review comments and threads:\n\n```bash\n# Inline review comments\ngh api repos\u002F{owner}\u002F{repo}\u002Fpulls\u002F{pr}\u002Fcomments\n\n# Review threads with resolution state (GraphQL)\ngh api graphql -f query='\n  query($owner:String!,$repo:String!,$pr:Int!){\n    repository(owner:$owner,name:$repo){\n      pullRequest(number:$pr){\n        reviewThreads(first:100){\n          nodes{ id isResolved comments(first:50){ nodes{ id body author{login} } } }\n        }\n      }\n    }\n  }' -F owner={owner} -F repo={repo} -F pr={pr}\n```\n\nReply to an inline review comment:\n\n```bash\ngh api repos\u002F{owner}\u002F{repo}\u002Fpulls\u002F{pr}\u002Fcomments\u002F{comment_id}\u002Freplies \\\n  -f body=\"Addressed in \u003Ccommit>: \u003Cexplanation>\"\n```\n\nResolve a review thread (needs the thread node id from the GraphQL query above):\n\n```bash\ngh api graphql -f query='\n  mutation($threadId:ID!){\n    resolveReviewThread(input:{threadId:$threadId}){ thread{ isResolved } }\n  }' -F threadId={thread_id}\n```\n",{"name":5,"description":7},"main","230a3aa0bba19b6bf5a7b4f427bcb25cb16c7105","python\u002F.github\u002Fskills\u002Fpull-requests",2624,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework","https:\u002F\u002Faka.ms\u002Fagent-framework","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 14:06:55",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add microsoft\u002Fagent-framework --skill pull-requests",{"tool":73,"command":74},"bunx","bunx skills add microsoft\u002Fagent-framework --skill pull-requests",{"tool":76,"command":77},"pnpm","pnpm dlx skills add microsoft\u002Fagent-framework --skill pull-requests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fpython\u002F.github\u002Fskills\u002Fpull-requests\u002FSKILL.md",true,[],[82,104,129,139,162,179],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":52},"01M70H1GNJPW85ENXA0BCPC6PF","draft-release-notes","Create or rewrite Agent Framework release notes from a generated GitHub release log. Use when preparing Python or .NET release notes, filtering mixed-language changelogs, deduplicating changes, preserving inline contributor credits, or documenting breaking-change migrations from pull requests. Requires the user to provide the generated GitHub log, language, and release version before work begins.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdraft-release-notes\u002FSKILL.md",[],[89,90,91,92,93,94,50,32,95,34,96,97,41,98,99,100,101,102,103,36],"notes","release notes","release","draft","draft release notes","python","create","generated","filtering","version","log","release version","rewrite","mixed-language","contributor",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":52},"01M699C55AYGT1ZVZDHWFZNBDB","agent-framework-builder-python","Use this skill when building, modifying, reviewing, evaluating, integrating, or hosting Python applications with Microsoft Agent Framework. Use it for Agent Framework agents, harness agents, workflows, orchestrations, declarative definitions, tools, sessions, middleware, evaluation, observability, integrations, or hosting, even when the user has not yet chosen the correct framework pattern.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fskills\u002Fagent-framework-builder-python\u002FSKILL.md",[110],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[94,50,112,45,113,9,114,115,116,117,118,119,120,121,122,41,123,124,125,126,127,38,128,36],"agent framework builder python","builder","workflows","sessions","microsoft agent framework","harness","observability","Evaluation","applications","correct","integrations","hosting","pattern","middleware","with","orchestrations","declarative",{"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":136,"publishedAt":52},"01M699C2PH4WPRCMV90NHANCY9","agent-framework-builder-dotnet","Use this skill when building, modifying, reviewing, evaluating, integrating, or hosting .NET (C#) applications with Microsoft Agent Framework. Use it for Agent Framework agents, harness agents, workflows, orchestrations, declarative definitions, tools, sessions, middleware, evaluation, observability, integrations, or hosting, even when the user has not yet chosen the correct framework pattern.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fskills\u002Fagent-framework-builder-dotnet\u002FSKILL.md",[135],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[50,137,138,45,113,9,114,115,116,117,118,120,121,122,41,125,126,127,38,128,36],"dotnet","agent framework builder dotnet",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":52},"01M699C0QKV5XEBE61PB8NV544","foundry-hosted-agent-validation","Step-by-step process for validating a Python Foundry hosted agent sample (under python\u002Fsamples\u002F04-hosting\u002Ffoundry-hosted-agents\u002F) end to end — running it locally (native runtime and `azd ai agent run`) and after deploying it to an Azure AI Foundry project with `azd`. Use this when asked to validate a hosted agent sample.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fpython\u002Fscripts\u002Fsample_validation\u002Fskills\u002Ffoundry-hosted-agent-validation\u002FSKILL.md",[145],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[147,148,149,94,150,151,152,153,45,154,155,41,156,157,158,159,160,38,36,161],"foundry","foundry hosted agent validation","validation","ai agent","azure","run","azure ai foundry","tool","model","project","sample","runtime","end","native","running",{"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":52},"01M699BYCYJD8RXC5MYY61WBPR","foundry-config-setup","Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder\u002Fhardcoded project_endpoint (for example \"https:\u002F\u002Fyour-project.services.ai.azure.com\") or a hardcoded model instead of reading them from the environment.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fpython\u002Fscripts\u002Fsample_validation\u002Fskills\u002Ffoundry-config-setup\u002FSKILL.md",[],[147,169,170,171,172,151,173,174,175,154,155,176,41,177,156,157,178,126,38,36],"foundry config setup","config","setup","placeholder","tool use","https","services","environment","example","missing",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":52},"01M699BWSTE6SGCCBY3JFP10GQ","support-style","Contoso Outdoors customer-support tone and formatting guidelines.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-framework\u002Fblob\u002Fmain\u002Fpython\u002Fsamples\u002F04-hosting\u002Ffoundry-hosted-agents\u002Fresponses\u002Ffoundry_toolbox_mcp_skills\u002Fskills\u002Fsupport-style\u002FSKILL.md",[],[186,187,188,189,190,191,192],"support","support style","style","customer","guidelines","tone","formatting"]