Update snap skill

[jjonescz]

Microsoft Reviewers: Open in CodeFlow

[azure-pipelines]

Azure Pipelines:
2 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]

Pull request overview

This PR updates the snap skill documentation to better reflect current snap workflows, especially around SDK servicing branches, subscription-driven SDK destination mapping, and post-snap operational steps.

Changes:

• Refines snap branch-cascade guidance, including preserving old stable content via a release/<sdk-band> servicing branch when needed.
• Adds a subscription-topology step to determine actual SDK destinations instead of inferring them solely from default channels.
• Expands execution guidance with reachability checks, milestone assignment based on git ancestry, and a manual InfraSwat dashboard update checkpoint.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

.github/skills/snap/SKILL.md:164

• The schedule-discovery instructions reference project_search/code_read methods that aren’t defined anywhere else in this repo’s skill set, so an agent following this will likely get stuck. Consider rewriting this section to be tool-agnostic (DevDiv wiki page + fallback to asking the user for a link/text) rather than naming specific, undefined MCP methods.

Use an MCP server to find the schedule:
1. Search the `DevDiv.wiki` repository in organization/project `devdiv/DevDiv` for `Dev{version} Schedule` with `project_search` method `wiki`.
2. Read the returned page path with `code_read` method `content`.
3. For the snapped version, extract:

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Suppressed comments (2)

Previously missed (1) — in code that hasn't changed since the last review.

.github/skills/snap/SKILL.md:618

• az repos pr create options are version-sensitive; passing boolean flags like --draft false --auto-complete true --squash true can fail or be ignored depending on Azure CLI/devops extension versions (and the script already has a verification/update block to enforce state). To make the skill more robust, create the PR with only required arguments, then rely on the subsequent az repos pr show/update block to set draft/autocomplete/squash.

$description = "Updates default channels for the {newVsVersion} snap. Auto-generated by snap skill."
az repos pr create --repository maestro-configuration --org https://dev.azure.com/dnceng --project internal --source-branch {cfgBranch} --target-branch production --title "Snap: update default channels for {repos} ({newVsVersion})" --description $description --draft false --auto-complete true --squash true -o none

.github/skills/snap/SKILL.md:163

• The schedule lookup references MCP methods (project_search with wiki and code_read with content) that aren’t defined elsewhere in this repo’s skills/docs, so it’s unclear what tool/environment this is targeting. Make this step tool-agnostic and include an explicit fallback (e.g., ask the user for a schedule link) so the skill remains usable when that MCP integration isn’t available.

Use an MCP server to find the schedule:
1. Search the `DevDiv.wiki` repository in organization/project `devdiv/DevDiv` for `Dev{version} Schedule` with `project_search` method `wiki`.
2. Read the returned page path with `code_read` method `content`.