whats-new
Skill119 starsChanged 3 months agoMITView on GitHub
Draft a "What's New" community update for the Revel Discord covering changes across backend, frontend, and infra over a time window. Use when the user runs /whats-new or asks for a community changelog/release-roundup post for organizers (and the programmers in the room).
9 other projects use a version of this.
Adopted by
Most recently taken up by
- Sn4kyGit/qa-agent-blueprinttheir own version, first seen Nov 16, 2026
- 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
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
- Snowflake-Labs/coco-skills★ 54same name
- Sn4kyGit/qa-agent-blueprint★ 2same 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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- loki-logsSkill
- silk-debugSkill
- update-changelogSkill
- updating-depsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
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
- Distinctive: line 38
Keep the human label for the header: "Last month" (1m), "Last 2 weeks" (2w), etc.
- Very specific: line 48
Read every ## [X.Y.Z] - DATE section with DATE >= cutoff, plus [Unreleased].
- Very specific: line 71
When a PR title is opaque, read its body for the user-facing description.
- Distinctive: line 95
Don't surface internal refactors, secrets, or per-PR links in the body.
- Distinctive: line 99
Every edition page must end with a footer linking the changelog(s) — include a repo only if it has a changelog.
- Very specific: line 106
Only list Frontend once ../revel-frontend/CHANGELOG.md exists.
“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
What's New
Produces a Discord-ready "What's New" post for the Revel community and archives it on the published docs site. Audience: mostly organizers, but programmers too — every item leads with the organizer-facing benefit and carries a light technical detail (a flag, an endpoint, a behavior change) for the developers reading along.
Three repos, all public, all siblings of the cwd (revel-backend):
| Repo | Path | Primary source |
| Backend | . (cwd) | CHANGELOG.md (rich, dated, user-facing prose) |
| Frontend | ../revel-frontend | CHANGELOG.md if present, else git/PR digging |
| Infra | ../infra | git/PR digging (no changelog) |
The frontend is adopting the backend's changelog process. Always check for
../revel-frontend/CHANGELOG.mdfirst and use it changelog-first when it exists; only fall back to git/PR digging for repos that have no changelog yet.
1. Parse the window
The argument is number + w|m (e.g. 1w, 2m, 6w). Default 1m if empty/unrecognized.
Compute the cutoff date (this is darwin/BSD date; for GNU use date -d "-2 months" +%F):
# N and UNIT parsed from the arg; UNIT is w (weeks) or m (months)
date -v-${N}${UNIT} +%F # e.g. date -v-1m +%F → cutoff YYYY-MM-DD
date +%F # today, for the edition headerKeep the human label for the header: "Last month" (1m), "Last 2 weeks" (2w), etc.
2. Gather changes (changelog-first, dig only gaps)
Backend — primary, already curated prose:
grep -nE '^## \[' CHANGELOG.md # locate version sections + datesRead every ## [X.Y.Z] - DATE section with DATE >= cutoff, plus [Unreleased]. These bullets
are already user-facing — reuse their substance. Open a PR (gh pr view <n>) only when an
entry is too terse to translate for a community audience.
Frontend — changelog-first if present, else git/PR:
test -f ../revel-frontend/CHANGELOG.md && echo "use changelog" || echo "dig git/PRs"
# changelog path: same as backend, against ../revel-frontend/CHANGELOG.md
# fallback path:
git -C ../revel-frontend log --since="<cutoff>" --first-parent --merges --pretty='%h %s'
gh -R letsrevel/revel-frontend pr list --state merged --search "merged:>=<cutoff>" \
--limit 50 --json number,title,body,mergedAtInfra — git/PR only:
git -C ../infra log --since="<cutoff>" --first-parent --merges --pretty='%h %s'
gh -R letsrevel/infra pr list --state merged --search "merged:>=<cutoff>" \
--limit 50 --json number,title,body,mergedAtWhen a PR title is opaque, read its body for the user-facing description. Drop the noise: pure CI/lint/test/dependency-bump/refactor commits unless they change observable behavior.
3. Compose — grouped by area
Group items into emoji-headed areas chosen from what's actually in the window. Suggested palette (use only the ones that apply; invent others as needed):
## 🎟️ Events & Tickets## 💳 Payments, VAT & Reporting## 🔔 Notifications & Comms## 📋 Questionnaires & Polls## 🌍 Self-hosting & Infrastructure## 🛠️ Under the Hood(perf, security, developer-facing)
Per bullet: organizer benefit first, light tech detail inline. Example:
- Mark an event as open-ended when there's no fixed finish — the page shows "Ongoing" instead of an end time (
is_open_endedflag, propagates to recurring series).
Rules:
- Discord markdown only:
##/###headers,**bold**,-bullets,`code`. No tables, no collapsibles. - Confident and community-friendly, concise, no marketing fluff.
- Don't surface internal refactors, secrets, or per-PR links in the body.
4. The changelog footer (REQUIRED on every edition page)
Every edition page must end with a footer linking the changelog(s) — include a repo only if it has a changelog. mkdocs has no auto-link extension, so use markdown links:
**📋 Full changelogs:** [Backend](https://github.com/letsrevel/revel-backend/blob/main/CHANGELOG.md) · [Frontend](https://github.com/letsrevel/revel-frontend/blob/main/CHANGELOG.md)Only list Frontend once ../revel-frontend/CHANGELOG.md exists; add Infra if/when it gets one.
5. Deliver
The published docs page is the canonical artifact; the Discord message is a short teaser that links to it.
a. Write a new edition page (one file per run):
docs/whats-new/<today>-last-<slug>.md, where <slug> is the window label kebab-cased —
1m→last-month, 2m→last-2-months, 1w→last-week, 2w→last-2-weeks. Example:
docs/whats-new/2026-06-22-last-month.md. Structure: # What's New — <date range> H1, the
area sections (##), then the §4 changelog footer.
b. Index it — prepend a bullet to docs/whats-new/index.md right after the
<!-- EDITIONS BELOW ... --> marker, newest first:
- [<date> — Last <window>](<filename-without-.md>.md) — <one-line teaser of the headline items>Also add the edition to the left-sidebar nav in mkdocs.yml, under the What's New: section
right after whats-new/index.md (newest first, matching the ADR section's per-entry layout):
- What's New:
- whats-new/index.md
- whats-new/<filename>.md # <-- prepend the new edition here, above older onesc. Print the Discord message in chat, inside a fenced block so it's copy-pasteable — a SHORT teaser, not the full post: a punchy intro line, 4–6 headline bullets (the biggest items only), and a link to the published edition page:
📖 Full update → https://docs.letsrevel.io/whats-new/<slug>/(The <slug> is the filename without .md. The URL goes live when docs deploy — that's expected;
say so.) Keep it comfortably under Discord's 2000-char limit.
d. Do not commit (project rule: always ask first). Report the new file, the index update, and print the Discord teaser, then offer to commit.
Notes
- The docs publish to https://docs.letsrevel.io under the "What's New" nav tab; each edition lives
at
https://docs.letsrevel.io/whats-new/<slug>/. - The edition page carries the full detail; the Discord teaser only summarizes and links to it.
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.

