release-notes

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

Repositorio: dotnet/fsharp
Última actividad en el origen: 1 de julio de 2026 a las 15:38
Idioma detectado de SKILL.md: inglés
Estrellas: 4322
Forks: 869

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

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.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

2 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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

Ver todos los de este repositorio

* 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

Opciones de instalación

Revisa los archivos de origen

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

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

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