whats-new
Skill2 starsChanged 8 days agoApache-2.0View on GitHub
Show what changed in the blueprint since a project was onboarded or re-boarded — renders the relevant CHANGELOG sections in the user's language, noting which changes call for /re-board. Use for "/whats-new", "was ist neu", "changelog", or right after a plugin update. Read-only; the apply step is /re-board.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- Snowflake-Labs/coco-skillstheir own version, first seen Nov 15, 2026
- CodeWithCJ/SparkyFitnesstheir own version, first seen Nov 1, 2026
- EtanHey/golemstheir own version, first seen Oct 28, 2026
- skyhook-io/radartheir own version, first seen Oct 25, 2026
- omnigami-ai/whats-newtheir own version, first seen Oct 20, 2026
- GopkoDev/motion-flowtheir own version, first seen Oct 20, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- CodeWithCJ/SparkyFitness★ 6.8ksame name
- skyhook-io/radar★ 4.1ksame name
- letsrevel/revel-backend★ 119same name
- Snowflake-Labs/coco-skills★ 54same name
- GopkoDev/motion-flow★ 1same name
- masem-at/claude-skills★ 1same name
- EtanHey/golems★ 0same name
- jayefel/claude-skills★ 0same name
- omnigami-ai/whats-new★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-testingSkill
- agentswitchSkill
- api-testingSkill
- bug-reportSkill
- bug-reproductionSkill
- demoSkill
- deploy-to-stageSkill
- exploratory-testingSkill
- failure-analysisSkill
- model-setupSkill
- onboard-productSkill
- onboard-projectSkill
- perf-analysisSkill
- qa-helpSkill
- qa-metricsSkill
- qa-reportSkill
- re-boardSkill
- reconSkill
- release-readinessSkill
- report-to-jiraSkill
- retest-bugSkill
- retro-learnSkill
- risk-based-testingSkill
- scaffold-suiteSkill
- security-testingSkill
- skill-reviewSkill
- test-automationSkill
- test-case-managementSkill
- test-reliabilitySkill
- test-ticketSkill
- visual-testingSkill
- webdriverio-testingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read the installed blueprint version from .claude-plugin/plugin.json (via the support link.
- Very specific: line 18
Read the Blueprint version stamps of all onboarded projects (projects/*/PROJECT.md, skipping _template and EXAMPLE).
- Very specific: line 52
Start a re-board, edit a project file, or "helpfully" apply a change.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/whats-new — what changed since this project was onboarded
Orientation only, like /qa-help: render the delta, then stop. Do not start
any work from it — if a change calls for action, the action is /re-board
and the user runs it next. Answer in the user's language.
Steps
- Read the installed blueprint version from
.claude-plugin/plugin.json(via the support link; plugin mode:$CLAUDE_PLUGIN_ROOT/.claude-plugin/plugin.json). - Read the
Blueprint versionstamps of all onboarded projects (projects/*/PROJECT.md, skipping_templateandEXAMPLE). No stamp = "pre-0.5.0" (the field did not exist yet). - In the blueprint's
CHANGELOG.md, take every version section NEWER than the oldest stamp across the projects. Sections are## [X.Y.Z] — date; stop at the first section that is not newer. Include[Unreleased]only when the running version is a dev checkout (installed version matches no section — practically: the blueprint repo itself). Render, in the user's language:
- one line per project:
<KEY>: onboarded at <stamp or "pre-0.5.0">, blueprint is at <installed> - the changelog entries between, grouped by version, compressed to what each change means for the user (one line each — the full CHANGELOG stays the reference, do not paste it verbatim)
- a closing line per change that touches project files: "betrifft
projects/<KEY>/…→/re-board <KEY>brings it up to date" — the version-stamp field itself, Secrets source, flow maps, and similar schema changes always qualify; pure plugin-internal changes (hooks, evals, docs) get "no project action needed".
Example shape (German user, one project):
SHOP: onboarded at 0.11.0, blueprint ist 0.12.0 **0.12.0 — wer am Steuer sitzt** - Ausführungsmodus pro Projekt wählbar (mcp-only / hybrid / cli-first) — betrifft projects/SHOP/PROJECT.md → /re-board SHOP bringt es auf Stand. - Neue Pipeline-Doku + /recon-Skill — kein Projekt-Eingriff nötig.- one line per project:
- Nothing to show (all stamps current): say so in one line and stop.
What this skill never does
Start a re-board, edit a project file, or "helpfully" apply a change. Update
the stamps itself (that is /re-board's job — a stamp that moves without the
project being upgraded makes this skill lie).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

