release-notes

Write release notes for completed changes. Use when PR modifies tracked paths and needs release notes entry.

Repository: dotnet/fsharp
Last source activity: July 1, 2026 at 15:38
Detected SKILL.md language: English
Stars: 4,322
Forks: 869

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/dotnet/fsharp --skill release-notes

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

fsharp-diagnostics

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.

2026-08-04

pr-description

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).

2026-07-28

code-compaction

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.

2026-07-01

View all from this repository

* Description. ([PR #NNNNN](https://github.com/dotnet/fsharp/pull/NNNNN))

dotnet fsi .github/skills/release-notes/pick-insert-line.fsx --sink <Sink> --section <Section>

release-notes

Install options

Review the source files

Release Notes

Version

Path

Sink Mapping

Format (Keep A Changelog)

Entry Format

Release Notes

Version

Path

Sink Mapping

Format (Keep A Changelog)

Entry Format

Where to insert (avoid merge conflicts)

CI Check

name	release-notes
description	Write release notes for completed changes. Use when PR modifies tracked paths and needs release notes entry.

release-notes

Source facts

Install options

Review the source files

More from this repository

More from this repository

Release Notes

Version

Path

Sink Mapping

Format (Keep A Changelog)

Entry Format

Release Notes

Version

Path

Sink Mapping

Format (Keep A Changelog)

Entry Format

Where to insert (avoid merge conflicts)

CI Check