Menú
Write release notes for completed changes. Use when PR modifies tracked paths and needs release notes entry.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Triage a build / compile / restore / WarnAsError failure from its MSBuild binary log. Fetches the binlog (a local build's, or a failed dotnet/fsharp Azure DevOps PR build's published artifact) and analyzes it live via the `binlog-mcp` MCP server — structured errors, root-cause diagnosis, and an MSBuild perf X-ray. NOT for test failures or CheckCodeFormatting: a build binlog has no errors there.
Investigate compiler failures, test errors, or unexpected behavior through systematic minimal reproduction, 3-hypothesis testing, and verification. Always re-run builds and tests after changes.
Retrieve and analyze Azure DevOps build failures for GitHub PRs. Use when CI fails. CRITICAL: Collect ALL errors from ALL platforms FIRST, write hypotheses to file, then fix systematically.
Use when drafting, proposing, creating, or editing prose for a dotnet/fsharp GitHub PR or issue — body, title, comment, review summary, edits — including bare asks like "open a PR", "ship this", "write up what I did", "summarise the change", "reply on the PR", "edit the issue body", "gh pr create", "gh pr comment", "gh pr edit --body", "gh issue comment", "gh pr review --body". Primary use case is PR descriptions; same rules apply to PR/issue comments and review summaries. Not for labels, reviewers, merging, or code-review findings (just the prose write-up of them).
Always invoke after editing `.fs` files under `src/Compiler/`. Fast parse/typecheck without `dotnet build`, plus symbol references and inferred type hints. Use whenever the user asks about F# errors, compile errors, type inference, finding usages, or renaming a symbol in the compiler tree.
Performs multi-agent, multi-model code review of F# compiler PRs across 19 dimensions including type checking, IL emission, binary compatibility, and IDE performance. Dispatches parallel assessment agents per dimension, consolidates with cross-model agreement scoring, and filters false positives. Invoke when reviewing compiler changes, requesting expert feedback, or performing pre-merge quality checks.
| name | release-notes |
| description | Write release notes for completed changes. Use when PR modifies tracked paths and needs release notes entry. |
From GitHub repo variable VNEXT (e.g., 10.0.300)
preview.md<VSMajorVersion>.vNext.mddocs/release-notes/.<Sink>/<Version>.md
.Language.FSharp.Core.VisualStudio.FSharp.Compiler.Service### Fixed
* Bug fix description. ([Issue #NNN](...), [PR #NNN](...))
### Added
* New feature description. ([PR #NNN](...))
### Changed
* Behavior change description. ([PR #NNN](...))
### Breaking Changes
* Breaking change description. ([PR #NNN](...))
* Description. ([PR #NNNNN](https://github.com/dotnet/fsharp/pull/NNNNN))* Description. ([Issue #NNNNN](...), [PR #NNNNN](...))PR fails if changes in tracked paths without release notes entry containing PR URL.
Add NO_RELEASE_NOTES label to skip.