What problem does it solve?
When a merged dotnet/runtime PR introduces a breaking change, the docs team needs a structured issue in dotnet/docs describing the change, its impact, and migration guidance. Writing these issues manually requires gathering PR context, determining the correct .NET release version, checking for duplicates, and following a strict issue template.
Core Features & Use Cases
- Automated PR context gathering: Reads PR metadata, diffs, comments, reviews, and closing issues from dotnet/runtime to understand the change.
- Release version detection: Runs a PowerShell helper that inspects release branches, tags, and backport PRs via the GitHub CLI to determine which .NET preview, RC, or GA release the change ships in.
- Duplicate checking and template compliance: Searches dotnet/docs for existing breaking-change issues and authors new ones following the official issue template with before/after code examples and migration guidance.
- Use Case: A PR labeled needs-breaking-change-doc-created is merged; the skill drafts the full issue body, builds a PR comment with a pre-filled issue-creation link, and posts it for the docs team.
Quick Start
Ask the assistant to document the breaking change in dotnet/runtime PR 114929 and review the generated draft before publishing.