snap

Coordinate cross-branch version bumps and channel migrations for Roslyn branch snaps.

4|1|Updated May 1, 2026
One-click install
npx skills add https://github.com/CoolCoderSuper/vb-ls --skill snap-coolcodersuper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: snap
Source: https://github.com/CoolCoderSuper/vb-ls/tree/main/roslyn/.github/skills/snap
Command: npx skills add https://github.com/CoolCoderSuper/vb-ls --skill snap-coolcodersuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch snaps coordinate release branch cuts across main, release/insiders, and release/stable for dotnet repos like dotnet/roslyn, ensuring version bumps and channel migrations happen in a controlled, auditable way.

Core Features & Use Cases

  • Automates the Gather, Plan, and Execute phases for Roslyn-style snaps, including PR generation and signaling for pre/post steps.
  • Uses a take-source merge strategy to apply content from the source branch to the target while preserving history and minimizing conflicts, and constructs target PublishData.json overrides per branch.
  • Updates critical configuration files (Versions.props, Razor Directory.Build.props for Razor scenarios), SARIF files, and darc default channels, while drafting pre-snap emails and milestone moves.
  • Handles interim PublishData.json adjustments for VS branch shifts, and provides a clear rollback/cleanup plan after the snap completes.

Quick Start

Review the current Roslyn repo state and initiate the branch snap workflow to align main, insiders, and stable with the next VS version.

Frequently Asked Questions about snap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a Roslyn branch snap across main, release/insiders, and release/stable?

A Roslyn branch snap is automated by coordinating cross-branch version bumps and channel migrations across main, insiders, and stable. The workflow handles PR generation, PublishData.json overrides, and darc default channel changes in an auditable way.

What does a darc channel migration involve during a dotnet branch snap?

A darc channel migration during a dotnet branch snap involves shifting default channels to align with the next Visual Studio version. The workflow also routes interim VS-branch shifts and adjusts PublishData.json to ensure builds target the correct release channels.

How do I update Versions.props and SARIF files when snapping Roslyn release branches?

To update Versions.props and SARIF files when snapping Roslyn release branches, the workflow automatically applies configuration updates during the Execute phase. It uses a take-source merge strategy to apply content from the source branch to the target.

Can I use a take-source merge strategy to preserve history during a dotnet multi-repo snap?

Yes, you can use a take-source merge strategy to apply content from the source branch to the target while preserving history and minimizing conflicts. This strategy is applied during the Execute phase across dotnet/roslyn-like repos.

What is the best way to handle rollback and cleanup after a Roslyn branch snap completes?

The best way to handle rollback after a Roslyn branch snap is to follow the provided cleanup plan after the snap completes. This ensures any interim PublishData.json adjustments or milestone moves can be safely reverted if issues arise.