Skip to content

Sync .github/skills directory with azure-sdk-tools for PR 16634 - #10220

Open
azure-sdk-automation[bot] wants to merge 23 commits into
mainfrom
sync-.github-skills-yuc/sdk-quality-skill-16634
Open

Sync .github/skills directory with azure-sdk-tools for PR 16634#10220
azure-sdk-automation[bot] wants to merge 23 commits into
mainfrom
sync-.github-skills-yuc/sdk-quality-skill-16634

Conversation

@azure-sdk-automation

Copy link
Copy Markdown
Contributor

Sync .github/skills directory with azure-sdk-tools for PR Azure/azure-sdk-tools#16634 See eng/common workflow

@azure-sdk-automation
azure-sdk-automation Bot requested review from Crystal YU (chunyu3) and a balanced review from Copilot August 10, 2026 06:21
@azure-sdk-automation
azure-sdk-automation Bot requested a review from a team as a code owner August 10, 2026 06:21
@azure-sdk-automation azure-sdk-automation Bot added EngSys This issue is impacting the engineering system. Central-EngSys This issue is owned by the Engineering System team. labels Aug 10, 2026
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.

Adds a new GitHub “skill” for detecting and mitigating Azure SDK breaking changes and wires up an evaluation trigger for CI gating, while adjusting the existing local-generation skill’s trigger/docs.

Changes:

  • Added azsdk-common-sdk-breaking-change skill documentation describing the breaking-change detection/mitigation workflow.
  • Added an eval YAML to trigger the breaking-change skill in CI.
  • Updated azsdk-common-generate-sdk-locally docs/triggers (removed “fix breaking changes” trigger and added a “generate only” note).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File Description
.github/skills/azsdk-common-sdk-breaking-change/evals/trigger.eval.yaml Introduces a CI-gate eval stimulus intended to invoke the new breaking-change skill.
.github/skills/azsdk-common-sdk-breaking-change/SKILL.md Defines the new skill, tools, and step-by-step breaking change detect/mitigate workflow.
.github/skills/azsdk-common-generate-sdk-locally/SKILL.md Updates trigger wording and adds guidance for “generate only” behavior.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@@ -0,0 +1,26 @@
name: azsdk-common-sdk-breaking-change-trigger-eval
description: Trigger and anti-trigger tests for theazsdk-common-sdk-breaking-change skill
Comment on lines +20 to +22
stimuli:
- name: trigger-detect-sdk-breaking-changes-for-service
prompt: "Detect and mitigate SDK breaking changes for the service webpubsub"
@@ -0,0 +1,26 @@
name: azsdk-common-sdk-breaking-change-trigger-eval
description: Trigger and anti-trigger tests for theazsdk-common-sdk-breaking-change skill
metadata:
version: "1.0.0"
distribution: shared
description: 'Detect and mitigate SDK Breaking changes for a SDK package which is generated from TypeSpec. WHEN: "Detect SDK breaking changes for a service", "Detect SDK breaking changes for an SDK package", "Detect and mitigate SDK breaking changes for a service", "Detect and mitigate SDK breaking changes for an SDK package". INVOKES: skill: azsdk-common-generate-sdk-locally; MCP tools: azsdk_customized_code_update, azsdk_package_detect_breaking_change.'
5. **Prompt the user to choose breaking changes to mitigate** — Present the list from step 3 as a multiple-choice selection.
6. **Mitigate SDK breaking changes** - Run `azure-sdk-mcp:azsdk_customized_code_update` with parameters:

- packagePath: The SDk package path
5. **Generate** — Run `azure-sdk-mcp:azsdk_package_generate_code` with the config file path.
6. **Build** — Run `azure-sdk-mcp:azsdk_package_build_code`. If build succeeds, proceed to step 8.
7. **Customize** — If build fails, or if user requests SDK modifications, run `azure-sdk-mcp:azsdk_customized_code_update` with the build errors or user request. The tool handles the full workflow internally: it classifies the issue, applies TypeSpec decorators and/or code patches, regenerates the SDK, and builds — all in one call. See [customization workflow](references/customization-workflow.md).
7. **Customize** — If build fails, or if user requests SDK modifications, run `azure-sdk-mcp:azsdk_customized_code_update` with the build errors or user request. The tool handles the full workflow internally: it classifies the issue, applies TypeSpec decorators and/or code patches, regenerates the SDK, and builds — all in one call. See [customization workflow](references/customization-workflow.md)._(If the user requested "generate only", stop here — skip steps 8–11.)_
@azure-sdk-automation
azure-sdk-automation Bot force-pushed the sync-.github-skills-yuc/sdk-quality-skill-16634 branch from e8ee844 to fb5408b Compare August 10, 2026 06:44
@azure-sdk-automation
azure-sdk-automation Bot force-pushed the sync-.github-skills-yuc/sdk-quality-skill-16634 branch 4 times, most recently from 033cc5e to 5085b25 Compare August 24, 2026 01:55
@azure-sdk-automation
azure-sdk-automation Bot force-pushed the sync-.github-skills-yuc/sdk-quality-skill-16634 branch 6 times, most recently from 95867d8 to 6641f5a Compare September 2, 2026 03:33
@azure-sdk-automation
azure-sdk-automation Bot force-pushed the sync-.github-skills-yuc/sdk-quality-skill-16634 branch from 6641f5a to a8e59dd Compare September 2, 2026 05:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Central-EngSys This issue is owned by the Engineering System team. EngSys This issue is impacting the engineering system.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants