Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
Writes and maintains .NET preview, RC and GA release notes from a scored features.json, working with sibling skills for change data, API diffs, code sample checks and review.
Install .NET Release Notes
$ npx skills add dotnet/core --skill release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dotnet/core release-notes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dotnet/core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/release-notes .claude/skills/release-notes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-notes" agent skill from https://github.com/dotnet/core/tree/main/.github/skills/release-notes into .claude/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dotnet/core/tree/main/.github/skills/release-notesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dotnet/core --skill release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dotnet/core release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/core.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/release-notes .agents/skills/release-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-notes" agent skill from https://github.com/dotnet/core/tree/main/.github/skills/release-notes into .agents/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dotnet/core --skill release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dotnet/core release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/core.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/release-notes .cursor/skills/release-notes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-notes" agent skill from https://github.com/dotnet/core/tree/main/.github/skills/release-notes into .cursor/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dotnet/core.git --path .github/skills/release-notes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dotnet/core --skill release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dotnet/core release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/core.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/release-notes .gemini/skills/release-notes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-notes" agent skill from https://github.com/dotnet/core/tree/main/.github/skills/release-notes into .gemini/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dotnet/core release-notesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dotnet/core --skill release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dotnet/core.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/release-notes .github/skills/release-notes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-notes" agent skill from https://github.com/dotnet/core/tree/main/.github/skills/release-notes into .github/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dotnet/core --skill release-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dotnet/core release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/core.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/release-notes .opencode/skills/release-notes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-notes" agent skill from https://github.com/dotnet/core/tree/main/.github/skills/release-notes into .opencode/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-notes- GitHub stars
- 22k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 531 words
- Files
- 16 (incl. references)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- MIT
At a glance
Writes and maintains .NET preview, RC and GA release notes from a scored features.json, working with sibling skills for change data, API diffs, code sample checks and review.
- Works in 8 steps: generate-changes diffs… → generate-features reads changes.json,… → update-existing-branch handles… → …
- Preparing release notes for a .NET preview, RC or GA milestone
- SKILL.md covers How it works, Local testing (no PRs), Existing-branch reruns and Reference documents
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This is the editorial writing stage of a multi-skill pipeline for the dotnet/core repository. generate-changes diffs source manifests between VMR refs to produce changes.json, generate-features scores and triages that into features.json, and update-existing-branch merges deltas when a milestone branch already exists. This skill then turns the higher-value entries into curated component markdown.
Before drafting, the agent confirms that features.json holds the real changes and commits from changes.json with scored candidates, not a schema stub. Public APIs are checked with api-diff-validation, code samples are built and run against the milestone build, and a multi-model review pass checks the notes against the scoring rubric. The output is a base pull request with shared metadata plus one pull request per component file, each aimed at the base branch so component teams review their own notes.
When your agent uses it
- Preparing release notes for a .NET preview, RC or GA milestone
- Re-running release notes on a branch that is already populated
- Selecting noteworthy features from a scored features.json
- Verifying documented APIs and code samples against the shipped build
- Running a final editorial review of release notes
Example prompts
- “Draft the runtime component release notes for the current preview from features.json.”
- “The milestone branch already has notes, so merge the new changes in without starting over.”
- “Check that every API mentioned in the SDK notes exists in the shipped build.”
- “Run the final editorial review pass on the release notes before we open the pull requests.”
Requirements
- The GitHub MCP server or the `gh` CLI for cross-repo queries
- The companion generate-changes, generate-features and review-release-notes skills
- Compatibility (from SKILL.md): Requires GitHub MCP server or gh CLI for cross-repo queries. Pairs with the generate-changes, generate-features, update-existing-branch, editorial-scoring, api-diff, api-diff-validation, validate-code-samples, and review-release-notes skills. Claude Opus 4.6 is the default workflow model; the preferred final reviewer pair is Claude Opus 4.6 + GPT-5.4 for broader editorial feedback.
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- generate-changes diffs source-manifest.json between VMR refs to produce changes.json
- generate-features reads changes.json, resolves revert/backout relationships, and emits features.json with optional scores using the shared…
- update-existing-branch handles incremental reruns when a milestone branch already exists, merging deltas instead of restarting from scratch
- api-diff-validation / dotnet-inspect verifies public APIs and confirms suspect features still exist in the shipped build; review the…
- release-notes writes curated component markdown using the higher-value entries from features.json. The base branch preallocates unlinked…
- validate-code-samples builds and runs the documented claims against the milestone build, catching what static API verification cannot see
- review-release-notes runs a final multi-model editorial QA pass against the scoring rubric and examples
- Output is a set of pull requests per release milestone in dotnet/core: a base PR that holds shared metadata (changes.json, features.json…
What it can do on your machine
Read from SKILL.md and the folder at commit 44927bc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires GitHub MCP server or gh CLI for cross-repo queries. Pairs with the generate-changes, generate-features, update-existing-branch, editorial-scoring, api-diff, api-diff-validation, validate-code-samples, and review-release-notes skills. Claude Opus 4.6 is the default workflow model; the preferred final reviewer pair is Claude Opus 4.6 + GPT-5.4 for broader editorial feedback.
From compatibility in the SKILL.md frontmatter.
Context cost
.NET Release Notes loads about 1.4k tokens when it runs, and up to ~26k if it reads all its reference files. Until then it costs about 135 tokens; SKILL.md has 531 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dotnet/core at commit 44927bc, republished under its MIT licence (© dotnet). 531 words, ~1,438 tokens.
Download SKILL.mdSave it as
.claude/skills/release-notes/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.- name
- release-notes
- description
- Generate and maintain .NET release notes from `features.json`. Uses `generate-changes` for authoritative shipped-change data, `generate-features` for scoring/triage, `update-existing-branch` for incremental reruns on populated branches, `editorial-scoring` for the shared rubric, `api-diff` to generate API diff reports, `api-diff-validation` for API verification, `validate-code-samples` to build and run the documented claims against the milestone build, and a multi-model `review-release-notes` pass for final editorial QA.
- compatibility
- Requires GitHub MCP server or gh CLI for cross-repo queries. Pairs with the generate-changes, generate-features, update-existing-branch, editorial-scoring, api-diff, api-diff-validation, validate-code-samples, and review-release-notes skills. Claude Opus 4.6 is the default workflow model; the preferred final reviewer pair is Claude Opus 4.6 + GPT-5.4 for broader editorial feedback.
.NET Release Notes
Generate and maintain release notes for .NET preview, RC, and GA releases.
This skill is the editorial writing stage of the pipeline. It turns a scored features.json file into the markdown that ships in this repository.
How it works
generate-changesdiffssource-manifest.jsonbetween VMR refs to producechanges.jsongenerate-featuresreadschanges.json, resolves revert/backout relationships, and emitsfeatures.jsonwith optional scores using the sharededitorial-scoringrubricupdate-existing-branchhandles incremental reruns when a milestone branch already exists, merging deltas instead of restarting from scratchapi-diff-validation/dotnet-inspectverifies public APIs and confirms suspect features still exist in the shipped build; review the incremental API diff for preview-to-preview migration signalsrelease-noteswrites curated component markdown using the higher-value entries fromfeatures.json. The base branch preallocates unlinked component entries inREADME.md; each component branch links its own entry when it adds the matching file. Seeformat-template.md.validate-code-samplesbuilds and runs the documented claims against the milestone build, catching what static API verification cannot seereview-release-notesruns a final multi-model editorial QA pass against the scoring rubric and examples- Output is a set of pull requests per release milestone in dotnet/core: a base PR that holds shared metadata (
changes.json,features.json,README.md,build-metadata.json) and one PR per component file and its index link. Each component PR targets the base branch so component teams review their own notes and matching index entry. Seepr-layout.mdfor the full layout and naming scheme.
Before drafting or delegating component files, confirm that the milestone's
features.json contains the real changes[] and commits{} from changes.json,
with matching change IDs and commit keys and scored candidates for noteworthy
changes. Do not substitute a schema stub or defer feature selection to the
component PRs. Give component writers the relevant candidate entries with
their scores and reasons rather than a slim list of titles and labels.
Before finalizing the milestone, run review-release-notes against the
changes.json, features.json, and completed component drafts on their
branches (or the base branch after they merge). Resolve noteworthy omissions
it finds or record the editorial reason in features.json.
Show full SKILL.md (184 more words)Show less
Local testing (no PRs)
To dry-run the skill against a milestone, only create the branch set locally. Don't push the branches or create the PRs.
Existing-branch reruns
When the milestone branch set already exists and contains drafted markdown, invoke
update-existing-branch. That shared
skill is the canonical playbook for refreshing changes.json, merging the delta
into features.json, integrating new material into existing sections, and
handling review comments without clobbering human edits.
Reference documents
- quality-bar.md — what good release notes look like
- vmr-structure.md — VMR branches, tags, source-manifest.json
- pr-layout.md — base + per-component branch layout
- ../update-existing-branch/SKILL.md — how to refresh a populated milestone branch set incrementally
- changes-schema.md — the shared
changes.json/features.jsonschema - ../editorial-scoring/SKILL.md — the reusable scoring rubric and cut guidance
- feature-scoring.md — how to score and cut features
- component-mapping.md — components, product slugs, output files
- format-template.md — markdown document structure
- editorial-rules.md — tone, attribution, naming
- api-verification.md — using dotnet-inspect to verify APIs
- ../validate-code-samples/SKILL.md — building and running the documented claims against the milestone build
- examples/ — curated examples from previous releases, organized by component. Read the examples for your component before writing. The examples/README.md lists 12 editorial principles derived from what works and what doesn't in past release notes.
© dotnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 15 other files (references) in .github/skills/release-notes of dotnet/core.
- SKILL.md
- references/api-verification.md
- references/changes-schema.md
- references/component-mapping.md
- references/editorial-rules.md
- references/examples/README.md
- references/examples/aspnetcore.md
- references/examples/csharp.md
- references/examples/libraries.md
- references/examples/runtime.md
- references/examples/sdk.md
- references/feature-scoring.md
- references/format-template.md
- references/pr-layout.md
- references/quality-bar.md
- references/vmr-structure.md
Open the folder on GitHubat commit 44927bc
Compare with similar skills
.NET Release Notes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| .NET Release Notes this skilldotnet/core | 22k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ccb GitHubSeemSeam/claude_codex_bridge | 3.5k | — | ~4.9k | Automated safety check: Pass | Custom licence | |
| Make Releaseatgreen/cl-tuition | 149 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Release Roslynatordotnet/roslynator | 3.5k | — | ~1k | Automated safety check: Pass | Custom licence | |
| Releasesol4k/sol4k | 135 | — | ~949 | Automated safety check: Pass | Apache-2.0 | |
| Maintain DisCatSharpAiko-IT-Systems/DisCatSharp | 140 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Make Release
atgreen/cl-tuition
Cut a new tuition release — verify release notes, tuition.asd version, README currency, a clean tree, and a green test suite, then tag vX.Y.Z and push so CI builds the GitHub release.
- Official
Release Roslynator
dotnet/roslynator
A skill your agent uses when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v release, or optionally tagging cli-v.
Release
sol4k/sol4k
Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.
Maintain DisCatSharp
Aiko-IT-Systems/DisCatSharp
Guides changes to the DisCatSharp C# Discord library: tracing a payload field through parsing, serialization and caches, then validating across target frameworks.
Release
emanuelcasco/pi-mono-extensions
Release a new version of pi-extensions: bump individual package versions (independent mode), update CHANGELOGs and READMEs, create per-package git tags, publish a GitHub release, and publish…
More from dotnet/core
All 15 skills in this repo- Official
Update .NET OS Packages
dotnet/core
Audits and updates os-packages.json files listing the Linux packages each .NET release needs per distro, then regenerates the Markdown from the JSON.
- Official
Update .NET Supported OS Matrix
dotnet/core
Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.
- Official
.NET Release Verification
dotnet/core
Validates .NET release data with the release-notes CLI: download URL liveness, SHA512 hashes, CDN latest.version files and aka.ms redirects.
- Official
Generate .NET Release changes.json
dotnet/core
Produces the changes.json manifest for a .NET preview, RC or GA milestone by choosing the right VMR base and head refs and running release-notes generate changes.
- Official
Release Feature Scoring
dotnet/core
Ranks the changes in a release manifest and writes a scored features file that release notes, docs and blog posts can each cut at their own threshold.
- Official
Release Notes Editorial Review
dotnet/core
Audits a scored features.json file and its draft release notes against editorial examples to catch over-scored, under-scored, or missing entries.
Related
Categories
Questions about .NET Release Notes
What does .NET Release Notes do?
Writes and maintains .NET preview, RC and GA release notes from a scored features.json, working with sibling skills for change data, API diffs, code sample checks and review. This is the editorial writing stage of a multi-skill pipeline for the dotnet/core repository.json, and update-existing-branch merges deltas when a milestone branch already exists.
When should I use .NET Release Notes?
.NET Release Notes fits situations like: preparing release notes for a .NET preview, RC or GA milestone; re-running release notes on a branch that is already populated; selecting noteworthy features from a scored features.json; verifying documented APIs and code samples against the shipped build.
How do I install .NET Release Notes in Claude Code?
Run `npx skills add dotnet/core --skill release-notes -a claude-code`. Or copy the skill folder (.github/skills/release-notes in dotnet/core) into .claude/skills/release-notes in your project. Claude Code loads it when a task matches its description.
How do I install .NET Release Notes in Codex?
Run `npx skills add dotnet/core --skill release-notes -a codex`. Or copy the skill folder (.github/skills/release-notes in dotnet/core) into .agents/skills/release-notes in your project. Codex loads it when a task matches its description.
Can I use .NET Release Notes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dotnet/core --skill release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-notes, .gemini/skills/release-notes, .github/skills/release-notes and .opencode/skills/release-notes in your project.
What does .NET Release Notes need to run?
SKILL.md names no scripts, command-line tools or credentials: .NET Release Notes is instructions for the agent only. Our summary lists: The GitHub MCP server or the `gh` CLI for cross-repo queries; The companion generate-changes, generate-features and review-release-notes skills. Compatibility (from SKILL.md): Requires GitHub MCP server or gh CLI for cross-repo queries. Pairs with the generate-changes, generate-features, update-existing-branch, editorial-scoring, api-diff, api-diff-validation, validate-code-samples, and review-release-notes skills. Claude Opus 4.6 is the default workflow model; the preferred final reviewer pair is Claude Opus 4.6 + GPT-5.4 for broader editorial feedback..
Does .NET Release Notes access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is .NET Release Notes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does .NET Release Notes use?
.NET Release Notes is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does .NET Release Notes use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 24k tokens, read only when the agent opens those files.
What are the alternatives to .NET Release Notes?
Skills that share tags, products or a category with .NET Release Notes: Ccb GitHub (SeemSeam/claude_codex_bridge, 3.5k stars), Make Release (atgreen/cl-tuition, 149 stars), Release Roslynator (dotnet/roslynator, 3.5k stars) and Release (sol4k/sol4k, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains .NET Release Notes?
dotnet (a GitHub organization, an official publisher) maintains it in dotnet/core, which has 22,038 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 5, 2026.
Source: dotnet/core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.