Fern Navigation
ai-dynamo/dynamo
Knowledge of Fern's site-level navigation and structure configuration — how a docs site is organized in docs.yml (and product/version .yml files) using sections, pages, folders, tabs, tab variants…
Step-argument skill that formalizes writing an Aspire "What's new in N.N" release-notes page (src/frontend/src/content/docs/whats-new/aspire-N-N.mdx) as a repeatable lifecycle.
Install Whatsnew
$ npx skills add microsoft/aspire.dev --skill whatsnew -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft/aspire.dev whatsnew --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/microsoft/aspire.dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/whatsnew .claude/skills/whatsnew && 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 "whatsnew" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/whatsnew into .claude/skills/whatsnew/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsnew", 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/microsoft/aspire.dev/tree/main/.agents/skills/whatsnewType 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 microsoft/aspire.dev --skill whatsnew -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft/aspire.dev whatsnew --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/whatsnew .agents/skills/whatsnew && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "whatsnew" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/whatsnew into .agents/skills/whatsnew/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsnew", 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 microsoft/aspire.dev --skill whatsnew -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft/aspire.dev whatsnew --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/whatsnew .cursor/skills/whatsnew && 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 "whatsnew" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/whatsnew into .cursor/skills/whatsnew/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsnew", 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/microsoft/aspire.dev.git --path .agents/skills/whatsnew--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 microsoft/aspire.dev --skill whatsnew -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft/aspire.dev whatsnew --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/whatsnew .gemini/skills/whatsnew && 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 "whatsnew" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/whatsnew into .gemini/skills/whatsnew/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsnew", 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 microsoft/aspire.dev whatsnewInstalls 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 microsoft/aspire.dev --skill whatsnew -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/whatsnew .github/skills/whatsnew && 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 "whatsnew" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/whatsnew into .github/skills/whatsnew/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsnew", 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 microsoft/aspire.dev --skill whatsnew -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft/aspire.dev whatsnew --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/whatsnew .opencode/skills/whatsnew && 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 "whatsnew" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/whatsnew into .opencode/skills/whatsnew/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whatsnew", 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
whatsnew- GitHub stars
- 196
- Token cost
- ~1.9k tokens
- SKILL.md length
- 667 words
- Files
- 9 (incl. references)
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Step-argument skill that formalizes writing an Aspire "What's new in N.N" release-notes page (src/frontend/src/content/docs/whats-new/aspire-N-N.mdx) as a repeatable lifecycle.
- : start/scaffold a new whats-new page for a release
- SKILL.md covers Dispatch on the modality…, Supporting references, Cross-cutting rules (apply to… and Key repository paths, plus 1 more section
- Calls pnpm
- Research a releases changes into a dossier and author the draft prose
What it does
Whatsnew is an agent skill from microsoft/aspire.dev, published by the product's own GitHub organization. Step-argument skill that formalizes writing an Aspire "What's new in N.N" release-notes page (src/frontend/src/content/docs/whats-new/aspire-N-N.mdx) as a repeatable lifecycle. Invoke as /whatsnew {modality} where modality is one of: draft/scaffold (init), research, critique, validate, polish, review. USE FOR: start/scaffold a new what's-new page for a release, research a release's changes into a dossier and author the draft prose, critique a draft, fact-check/validate the diff, polish and run data ingestion, or…
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `references/01-draft-scaffold.md`, `references/02-research.md` and `references/03-critique.md`).
It sits in Development, covering Changelog and release notes, Markdown and Data pipelines and ETL. The repository describes itself as: The official website for all things aspire.dev. The licence is MIT.
When your agent uses it
- : start/scaffold a new whats-new page for a release
- Research a releases changes into a dossier and author the draft prose
- Critique a draft
- Fact-check/validate the diff
Example prompts
- “s new in N.N”
- “s-new page for a release, research a release”
- “/whatsnew”
What it can do on your machine
Read from SKILL.md and the folder at commit 6f96d23. 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
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
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.
Context cost
Whatsnew loads about 1.9k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 202 tokens; SKILL.md has 667 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 microsoft/aspire.dev at commit 6f96d23, republished under its MIT licence (© microsoft). 667 words, ~1,851 tokens.
Download SKILL.mdSave it as
.claude/skills/whatsnew/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- whatsnew
- description
- Step-argument skill that formalizes writing an Aspire "What's new in N.N" release-notes page (src/frontend/src/content/docs/whats-new/aspire-N-N.mdx) as a repeatable lifecycle. Invoke as `/whatsnew {modality}` where modality is one of: draft/scaffold (init), research, critique, validate, polish, review. USE FOR: start/scaffold a new what's-new page for a release, research a release's changes into a dossier and author the draft prose, critique a draft, fact-check/validate the diff, polish and run data ingestion, or sign off the PR. DO NOT USE FOR: general docs pages (use doc-writer), reviewing an arbitrary docs PR (use doc-pr-reviewer), or product-repo changes. ORCHESTRATES: doc-writer, doc-pr-reviewer, doc-tester, twoslash-validator, update-integrations, update-samples, container-images.
What's-new release-notes skill
Formalizes the previously ad-hoc process of writing an Aspire "What's new in
Aspire N.N" page as a single, step-argument skill with a repeatable lifecycle.
Invoke it as /whatsnew {modality} — the modality argument selects one phase:
{draft/scaffold} → {research} → {critique} → {validate} → {polish} → {review}
init/structure dossier+draft self-review fact-check edits+data sign-offEach phase has a dedicated spec under references/. This skill
orchestrates existing skills — it does not duplicate them. {research} is the
phase that authors the article body from its dossier; {critique}/{validate}
then review and fact-check that draft, and {polish} finalizes it. Because
{polish} edits content after {validate}, it must end with a fresh
{validate} pass so nothing ships unchecked (see below).
Dispatch on the modality argument
Read the argument, then follow the matching spec. draft, scaffold, and init
are aliases for the same phase. If no argument is given, ask which phase to run (or
infer from context — e.g. a fresh release with no page → draft).
| Modality | Alias | Purpose | Spec | Edits content? |
|---|---|---|---|---|
draft | scaffold, init | Stand up branch, draft PR, skeleton MDX, banner, sidebar, version constants. Structure only. | 01-draft-scaffold.md | Skeleton only |
research | — | Enumerate every change into an impact-focused dossier, then author the first-draft prose into the MDX from it. | 02-research.md | Yes — drafts the body |
critique | — | Content-quality self-review of draft vs dossier; severity-ranked findings. | 03-critique.md | No — reports only |
validate | — | Ralph loop with doc-pr-reviewer until 100% factual; samples/links/assets. No pnpm build. | 04-validate.md | Fixes only |
polish | — | Editorial pass + CI triage + diagnostics-author @mentions + automated data ingestion, then a final {validate} pass. | 05-polish.md | Yes |
review | — | Undraft PR, description, reviewers + doc-tester blind run of every in-article scenario. | 06-review.md | No |
Supporting references
whats-new-template.mdx— structure-only skeleton thedraftphase copies (scaffold tokens,publishDatefrontmatter, and the mandated section taxonomy).writing-guidelines.md— humanized voice + the maintainer content standards. Defers todoc-writerfor canonical style.
Cross-cutting rules (apply to every phase)
Git / branching / PR
- Release work happens on a
release/{N.N}branch in the repository. - Cut
release/{N.N}from the latest default branch (e.g.main) — fetch first so you branch from an up-to-date base and avoid merge conflicts. - Iterate via a draft PR from
release/{N.N}into the repository's default branch. Open it after the scaffold is committed (a branch with no commits ahead of the default branch has no diff, so the PR can't be created);{review}marks it ready for review.
Show full SKILL.md (300 more words)Show less
Voice & quality (see writing-guidelines.md + doc-writer)
- Impact first, positives first, KISS. No walls of text, no marketing fluff.
- Judicious
<Aside>— a spotlight, not a floodlight. Don't burn the reader's eyes. - Content standards: Deployment and Integrations are separate sections; a
distinct "New integrations" section for brand-new ones; a "Default container
image updates" section for tag bumps. The release-date badge + GitHub release-notes
link render automatically from
publishDate+ slug — never hand-place them. - Resource artwork: Every new release page must set
resourceImageto newly captured screenshots demonstrating a feature introduced in that release, with matchinglight/darkvariants. Verify the running product version and capture its actual UI; do not substitute generic dashboard artwork, an older release's screenshots, or fabricated UI. Store the files in the release's assets folder before adding their paths, and show them beside the feature in the article. The resource directory discovers release pages and consumes this frontmatter automatically; do not add a duplicate catalog entry. Verify the card's image and release metadata in the resource-catalog tests and browser preview.
Safety / mechanics
- Never run
pnpm buildlocally — validate build-readiness by inspection. - Each modality is idempotent — safe to re-run;
critique/validateloop to convergence. - Re-validate after polish. Any edit
{polish}makes lands after the{validate}gate, so{polish}must finish with a fresh{validate}pass and{review}confirms it — the committed article never bypasses validation. - Prefer built-in tools over shell; Windows-friendly paths.
Key repository paths
| What | Path |
|---|---|
| What's-new pages | src/frontend/src/content/docs/whats-new/aspire-N-N.mdx (JA under .../ja/whats-new/) |
| Version constants | src/frontend/config/aspire-versions.mjs (currentAspireMajorMinorVersion, currentAspireVersion, currentAspireReleaseDate, currentAspirePreviewVersion) |
| Sidebar | src/frontend/config/sidebar/docs.topics.ts (What's-new items) |
| Announcement banner | banner: frontmatter on src/frontend/src/content/docs/index.mdx, src/frontend/src/content/docs/docs.mdx, src/frontend/src/content/docs/community/index.mdx, and each src/frontend/src/content/docs/{locale}/index.mdx (+ .../ja/docs.mdx); rendered by src/frontend/src/components/starlight/Banner.astro |
| Assets | src/frontend/src/assets/whats-new/aspire-<version>/ |
| Container image data | src/frontend/src/data/container-images.json |
| Diagnostics articles | src/frontend/src/content/docs/diagnostics/aspire<area><NNN>.mdx → /diagnostics/aspire<NNN>/ |
| Data ingestion | src/frontend/scripts/update-integration-data.ps1 (pnpm update:all) |
Orchestrated skills
doc-writer (voice/style) · doc-pr-reviewer (validate loop) · doc-tester (review
blind run) · twoslash-validator (TS samples) · update-integrations /
update-samples / container-images (polish data ingestion).
© microsoft, 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 8 other files (references) in .agents/skills/whatsnew of microsoft/aspire.dev.
- SKILL.md
- references/01-draft-scaffold.md
- references/02-research.md
- references/03-critique.md
- references/04-validate.md
- references/05-polish.md
- references/06-review.md
- references/whats-new-template.mdx
- references/writing-guidelines.md
Open the folder on GitHubat commit 6f96d23
Compare with similar skills
Whatsnew 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 |
|---|---|---|---|---|---|---|
| Whatsnew this skillmicrosoft/aspire.dev | 196 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Fern Navigationai-dynamo/dynamo | 8.2k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Changelog Writerjihe520/mindpocket | 349 | — | ~1.1k | Automated safety check: Pass | None | |
| MCP Apps Sync Docsapollographql/apollo-mcp-server | 311 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Curate Whats Newdocker/docs | 4.7k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Changelog Entrieshugodemenez/deltalytix | 159 | — | ~1.8k | Automated safety check: Pass | Custom licence |
Similar skills
Changelog Writer
jihe520/mindpocket
A skill your agent uses when the user wants to create or update a changelog, release notes, product updates, or an MDX changelog page from git history or local code changes.
MCP Apps Sync Docs
apollographql/apollo-mcp-server
Syncs MCP Apps documentation with the @apollo/client-ai-apps changelog.
- Official
Curate Whats New
docker/docs
Curate noteworthy Docker launches from documentation pull requests merged during a requested period.
Changelog Entries
hugodemenez/deltalytix
Write new bilingual English and French Deltalytix changelog entries from a reviewed release outline.
Release
Pipelex/pipelex
Cut a release of pipelex, which ships the pipelex and pipelex-api packages and the pipelex/pipelex-api Docker image under one version: the gates, the migration-ledger cross-check, the CHANGELOG.md…
More from microsoft/aspire.dev
All 8 skills in this repo- Official
Aspire
microsoft/aspire.dev
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.
- Official
Container Images
microsoft/aspire.dev
Extracts all container image references (registry, image, tag) from the microsoft/aspire source code and produces a JSON data file for the aspire.dev Astro site.
- Official
Doc Writer
microsoft/aspire.dev
Guidelines for producing accurate and maintainable documentation for the Aspire documentation site.
- Official
Twoslash Validator
microsoft/aspire.dev
Validate and fix two-slash TypeScript examples for aspire.dev.
- Official
Update Samples
microsoft/aspire.dev
Update the samples data file by fetching sample metadata from the microsoft/aspire-samples GitHub repository.
- Official
Update Integrations
microsoft/aspire.dev
Update integration documentation links and API reference data by synchronizing NuGet package names with their documentation URLs and generating per-package API schemas.
Related
Categories
Questions about Whatsnew
What does Whatsnew do?
Step-argument skill that formalizes writing an Aspire "What's new in N.N" release-notes page (src/frontend/src/content/docs/whats-new/aspire-N-N.mdx) as a repeatable lifecycle. dev, published by the product's own GitHub organization.mdx) as a repeatable lifecycle.
When should I use Whatsnew?
Whatsnew fits situations like: : start/scaffold a new whats-new page for a release; research a releases changes into a dossier and author the draft prose; critique a draft; fact-check/validate the diff.
How do I install Whatsnew in Claude Code?
Run `npx skills add microsoft/aspire.dev --skill whatsnew -a claude-code`. Or copy the skill folder (.agents/skills/whatsnew in microsoft/aspire.dev) into .claude/skills/whatsnew in your project. Claude Code loads it when a task matches its description.
How do I install Whatsnew in Codex?
Run `npx skills add microsoft/aspire.dev --skill whatsnew -a codex`. Or copy the skill folder (.agents/skills/whatsnew in microsoft/aspire.dev) into .agents/skills/whatsnew in your project. Codex loads it when a task matches its description.
Can I use Whatsnew 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 microsoft/aspire.dev --skill whatsnew -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/whatsnew, .gemini/skills/whatsnew, .github/skills/whatsnew and .opencode/skills/whatsnew in your project.
What does Whatsnew need to run?
Going by SKILL.md and its folder, Whatsnew needs the command-line tools its instructions call (pnpm).
Does Whatsnew 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 Whatsnew 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 Whatsnew use?
Whatsnew 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 Whatsnew use?
About 1.9k tokens (SKILL.md is roughly 7.4k 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 10k tokens, read only when the agent opens those files.
What are the alternatives to Whatsnew?
Skills that share tags, products or a category with Whatsnew: Fern Navigation (ai-dynamo/dynamo, 8.2k stars), Changelog Writer (jihe520/mindpocket, 349 stars), MCP Apps Sync Docs (apollographql/apollo-mcp-server, 311 stars) and Curate Whats New (docker/docs, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Whatsnew?
microsoft (a GitHub organization, an official publisher) maintains it in microsoft/aspire.dev, which has 196 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 8, 2026.
Source: microsoft/aspire.dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.