release-highlights
Skill4 starsChanged 12 days agoMITView on GitHub
Write the in-app "What's New" highlights for a Filbert release — add the version's entry to Sources/App/Resources/ReleaseHighlights.json, with one plain sentence per feature or fix in every supported language. Use this after the release-notes skill, or whenever the user asks for "highlights", "what's new text", or the release workflow fails because the version has no highlights entry.
- Commits and pushes
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Lingyan000/fluxdotheir own version, first seen Nov 16, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- garfiec/Librechat-Mobiletheir own version, first seen Nov 11, 2026
- leanprover/lean4their own version, first seen Oct 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- leanprover/lean4★ 10ksame name
- Lingyan000/fluxdo★ 2.6ksame name
- muxy-app/muxy★ 2.4ksame name
- garfiec/Librechat-Mobile★ 160same 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- release-notesSkill
- writing-codeSkill
- writing-specsSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 3 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
After an update, Filbert shows a short list of what is new in each version.
- Distinctive: line 14
Never touch git. Edit the file, validate it, and give the user the commands.
- Very specific: line 18
Ask for the version, or read it from the draft release: gh release list --limit 5.
- Very specific: line 20
Read the source text: gh release view v<version> --json isDraft,body.
- Distinctive: line 22
Use only the Overview, Features, and Bug Fixes sections.
- Very specific: line 26
If there is no Features and no Bug Fixes section, write an entry with an empty items list.
- Very specific: line 49
Write a value for every language in Sources/App/SupportedLanguage.swift.
- Very specific: line 52
Read docs/localization-glossary.md first.
- Very specific: line 64
Add the entry at the top of the list.
- Very specific: line 65
Keep the existing format: two-space indent, kind then text, languages in the order above.
- Distinctive: line 79
Run both. Fix the entry until they pass.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Release highlights
After an update, Filbert shows a short list of what is new in each version. Sparkle's
update dialog shows the same list in English. The text comes from
Sources/App/Resources/ReleaseHighlights.json, which ships inside the app. So the entry
must be merged to main before the release is published. The release workflow fails
when the entry is missing.
Never touch git. Edit the file, validate it, and give the user the commands.
1. Find the version and the source text
- Ask for the version, or read it from the draft release:
gh release list --limit 5. The version is the tag without thev, for example0.26.0. - Read the source text:
gh release view v<version> --json isDraft,body. If the user just ran therelease-notesskill, use that text. - Use only the Overview, Features, and Bug Fixes sections. Do not read the Changes list, commits, or PRs. The highlights say less than the release notes, never more.
If there is no Features and no Bug Fixes section, write an entry with an empty items
list. That tells the app that this release has nothing to show.
2. Write the English items
At most 5 items. Pick what a user notices. Merge small related changes into one item.
Each item:
- has
kindfeature(something new the user can do or see) orfix(something that was broken and now works); - is one sentence, at most 140 characters, ending with
.; - says what the user sees, not how the code works;
- uses plain words. No Markdown, links, HTML, emoji, or version numbers;
- names a provider the way the app does: Claude Code, Codex, Cursor, DeepSeek, Gemini CLI, Kimi API, Kimi Code, OpenCode Go, Z.ai;
- claims nothing that the source text does not say.
Good: Kimi Code's weekly and monthly rows now show when the allowance runs out.
Bad: Refactored KimiCodeForecast to use the shared pacing engine (#108).
3. Translate
Write a value for every language in Sources/App/SupportedLanguage.swift. Today:
en, de-DE, es-MX, es-ES, pt-BR, pt-PT, ru, zh-Hans, zh-Hant, ja.
- Read
docs/localization-glossary.mdfirst. Use its terms and follow its deny lists. The tests fail on a denied term. - Carry the meaning in the language's own idiom, not word for word.
es-MXandes-ES, andpt-BRandpt-PT, are separate. Write each one for its region, even when the words come out the same.zh-Hantuses Taiwan terms, with no space between Han characters and Latin letters or digits.jahas no space between kana or kanji and Latin letters or digits.- "Filbert" and provider names stay in Latin letters.
- Each value is one line, with no Markdown.
4. Edit the file
Add the entry at the top of the list. If the version is already there, replace it.
Keep the existing format: two-space indent, kind then text, languages in the order
above.
{
"version": "0.26.0",
"items": [
{ "kind": "feature", "text": { "en": "…", "de-DE": "…", "…": "…" } }
]
}5. Validate
Run both. Fix the entry until they pass.
python3 scripts/validate-release-highlights.py --require-version <version>
swift test --filter AppTests.ReleaseHighlightsTestsThe first checks the shape, the languages, and the English rules. The second checks the glossary deny lists and the Traditional Chinese characters.
6. Hand off
Show the user:
- The English items, as a list with their kind.
- A note that the translations need a native review before the merge.
- The commands to run. Do not run them:
git switch -c release-highlights/v<version>
git add Sources/App/Resources/ReleaseHighlights.json
git commit -m "chore: add release highlights for <version>"
git push -u origin release-highlights/v<version>
gh pr create --fill --base mainThen remind the user of the order: merge this PR, then publish the release.
Before you hand it back
- The entry is at the top, and its version matches the release.
- Every item comes from the Overview, Features, or Bug Fixes text.
- At most 5 items. Each English text is one sentence of 140 characters or fewer.
- Every supported language has a value.
- Both validation commands pass.
- You gave the git commands and did not run them.
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.

