メニュー
Write release notes for completed changes. Use when PR modifies tracked paths and needs release notes entry.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/dotnet/fsharp --skill release-notesコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
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.
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).
Use when a code/test/comment diff is called bloated, slop, LLM slop, bullshit, WTF, crap, rubbish, embarrassing, overengineered, adhoc, or "not paid by LOC"; or when symptoms include bloated comments, superfluous planning .md / .tools / one-time setup / phase-or-sprint tags, huge-file growth instead of new-file extraction, 5 copy-pasted tests that should be 1 parametrized test, duplicated test setup, reinvented helpers, near-duplicate logic across files, low reuse, 4+ new module-level helpers for one bugfix, fresh whole-AST/IR/syntax-tree walkers, or 150+ added LOC for one bugfix. Also use proactively before opening a PR whose diff smells like any of the above.
SOC 職業分類に基づく
| 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](...))Do NOT prepend at the top of the section — every PR doing that guarantees a merge conflict. Instead, insert at a random line within the target section using the helper, then edit there:
dotnet fsi .github/skills/release-notes/pick-insert-line.fsx --sink <Sink> --section <Section>
<Sink>: FSharp.Compiler.Service | FSharp.Core | Language | VisualStudio (no leading dot).<Section>: Fixed | Added | Changed | Breaking Changes | etc.--sink auto-selects the newest version file on disk, which can differ from the
VNEXT-targeted version (e.g. on servicing branches). When the version is known, prefer
passing the explicit path: --file docs/release-notes/.<Sink>/<Version>.md --section <Section>.It prints an anchor line (number + verbatim text) and whether to insert ABOVE or BELOW it.
Use the printed line as the edit anchor (old_str = the line; new_str places your bullet
on the indicated side). If it reports the section is missing, add the section first.
PR fails if changes in tracked paths without release notes entry containing PR URL.
Add NO_RELEASE_NOTES label to skip.