changewaves

Manage MSBuild Change Waves: create new waves, condition features behind opt-out flags, write tests for wave-gated features, document change waves in ChangeWaves.md, and retire expired waves. Use when adding changes that need an opt-out or rotating out old change waves. Changes that introduce a user-visible behavior change should consider whether to use a changewave.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-structured lifecycle guide that defers detail appropriately to referenced wiki docs and provides a useful checklist. It could be more actionable by inlining the C# feature-conditioning example and adding an explicit validation feedback loop.

Suggestions

Inline a short, executable C# example of conditioning a feature on AreFeaturesEnabled instead of only pointing to ChangeWaves-Dev.md, so the core action is copy-paste ready.

Add an explicit validation/feedback checkpoint after Step 3 (e.g., 'Run the new and opt-out tests; if the opt-out test fails, fix the conditioning and re-run') to strengthen the workflow loop.

Clarify in Step 1 exactly where to read the current MSBuild version (eng/Versions.props is named only in the checklist), so the version-lookup action is self-contained.

Dimension	Reasoning	Score
Conciseness	Lean and efficient; assumes Claude's competence, defines only the domain-specific concept ('Change Wave is an opt-out flag') and never pads with general MSBuild or programming background, so every token earns its place.	5 / 5
Actionability	Provides concrete file paths ('src/Framework/ChangeWaves.cs', 'eng/Versions.props') and a copy-paste documentation snippet, but defers the executable C# conditioning code to ChangeWaves-Dev.md rather than showing it inline, leaving a minor gap.	4 / 5
Workflow Clarity	A clear numbered sequence (Steps 1–4) plus a checklist gives a well-ordered process, and 'add at least one test that verifies the old behavior is preserved when the wave is opted out' acts as an implicit checkpoint, but there is no explicit validate-fix-retry feedback loop.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep, clearly signaled references to ChangeWaves-Dev.md and ChangeWaves.md; the SKILL.md stays an overview while detail lives in the referenced wiki docs.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that covers the full lifecycle of change waves and provides an explicit 'Use when' trigger. Slightly jargon-heavy in its trigger terms but otherwise clear and distinct.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions — 'create new waves, condition features behind opt-out flags, write tests for wave-gated features, document change waves in ChangeWaves.md, and retire expired waves' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Clearly answers 'what' with five enumerated actions and explicitly answers 'when' with a 'Use when adding changes that need an opt-out or rotating out old change waves' trigger clause.	5 / 5
Trigger Term Quality	Includes natural terms like 'change waves', 'opt-out', 'rotating out old change waves', and 'user-visible behavior change', but is somewhat jargon-bound and lacks synonyms or file extensions; a few common phrasings users might say are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear MSBuild-specific niche with distinct opt-out/rotating-wave triggers, making overlap with unrelated skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 6 suspicious	Warning

	Total	14 / 16 Passed

Repository: dotnet/msbuild
Path: .github/skills/changewaves/SKILL.md
Commit: b75ae9e

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.