| name | changelog |
| description | Draft a CHANGELOG.md entry for the current change — pick a representative emoji, write the text in 6th-grade plain language, link any mentioned public routes to wordplay.dev, and cite the relevant issue/PR. Invoke via /changelog after finishing a user-visible change. |
/changelog
Draft a CHANGELOG entry for the current change in this repo.
Every bullet in every section gets an emoji prefix. Visual consistency across Added/Changed/Fixed/Removed is the whole point. Skip the screenshot route entirely — production URL links (below) are easier to maintain and give readers a one-click path to see the change in action.
The line must start with a single representative emoji + space — the parser in scripts/updates.js reads this prefix and the in-app updates page renders it as an inset marker beside the text.
When to invoke
- User typed
/changelog.
- User asked you to update the changelog.
- You just finished a user-visible change and the user said yes to your offer to draft an entry.
Do not run unprompted. Always confirm with the user before writing to CHANGELOG.md.
Workflow
1. Understand the change
git status
git diff
git log -5 --oneline
Group related diffs into one bullet per user-visible behavior — not one bullet per file. If there are several unrelated changes, draft separate bullets.
2. Pick a section
| Heuristic | Section |
|---|
| New feature, dialog, output type, or built-in | Added |
| Reworked behavior or visual change to an existing feature | Changed |
| Bug fix to existing behavior | Fixed |
| Feature/UI/file removed | Removed |
| Test-only, comment-only, dependency bumps, doc cleanups | skip — no entry |
When uncertain, ask the user.
3. Pick an emoji
| Category | Emoji |
|---|
| Localization / new language | 🌐 |
| Glyph / font / typography | 🔣 🔠 |
| Build / tooling / infrastructure | 🛠️ |
| Audio / sound | 🔊 |
| Animation / motion | 🎞️ |
| Physics | 🧲 |
| Layout primitives | 🧱 📐 |
| Security / permissions | 🔒 🔑 |
| Documentation / how-to | 📖 |
| Conflict / type-checking | 🚦 |
| Persistence / sync | 💾 |
| Performance | ⚡ |
| Editor / text input | ✍️ 📝 |
| Autocomplete / menu suggestions | 💡 |
| Mouse / pointer / scroll | 🖱️ |
| Copy / paste | 📋 |
| Visual / contrast / dark mode | 🎨 🌙 |
| Blocks editing | 🧩 |
| Tour / navigation aid | 🧭 |
| Sharing / gallery collaboration | 🤝 |
| Generic bug fix (no category) | 🐛 |
| Removal / cleanup | 🧹 |
Deviate when something else fits better. The emoji prefix must be a single extended-pictographic grapheme (including VS16 modifier sequences like 🛠️) followed by a space, or the parser won't detect it.
4. Write the text
The sentence after the emoji is read by teachers and youth (per the file's preamble):
- Reading level: 6th grade. Short words, concrete verbs, no jargon. Wordplay identifiers like
@Phrase, Bind, @Hand stay as-is because they're language constructs — but don't surround them with engineering vocabulary ("subsystem", "memoization", "race condition", "regression").
- Length: 1–2 sentences max. If you need more, the change is probably two bullets, not one.
- Voice: first person plural ("We added…", "We made…", "We fixed…"). Match the existing style.
- Cite the source. If a GitHub issue or PR motivated the change, append
(#1234) at the end of the sentence — the page renders these as clickable GitHub links. To find one: check recent commit messages (git log --oneline -20) for (#N) references, or gh pr list --state merged --search '<keyword>' for recent PRs. Cite at most two numbers per bullet. Skip the citation only if no related issue/PR exists.
Bad: "Refactored the autocomplete subsystem to defer suggestion materialization, eliminating UI thread blocking during keystroke input."
Good: "We made auto-complete during typing less aggressive and annoying. (#1058)"
5. Link mentioned public routes to production
Production lives at https://wordplay.dev. When the entry text mentions a feature that maps cleanly to a public route (no auth, no project state), wrap the relevant phrase in a markdown link so readers can jump straight to it. The page renderer converts [text](url) into Wordplay markup <text@url> automatically.
Public routes to link to (verified non-auth):
Skip linking when:
- The feature lives inside the editor (
/project/...), gallery editor, or any auth-gated state — readers can't navigate there from a cold link.
- The mention is too generic to anchor to a single route ("on long pages", "in the editor", "in dialogs").
- The phrase doesn't read naturally as a link.
Examples:
- ✅
📖 Added 11 new built-in how-to's to the [Guide](https://wordplay.dev/guide)...
- ✅
🙏 We added a [thank you page](https://wordplay.dev/thanks) showing all of our GitHub contributors...
- ❌
🎨 We fixed a [text selection](https://wordplay.dev/) bug in the editor. (editor isn't a single public URL)
- ❌
⬆️ We added a [back to top](https://wordplay.dev/guide) button on long pages. (too generic — picking one example URL is arbitrary)
At most one link per bullet — multiple links inside a single sentence read as link soup.
6. Insert into CHANGELOG.md
- Open CHANGELOG.md.
- Find the top
## <version> - <date> section. If a new version section is appropriate (e.g., a release just happened), ask the user before creating one — version bumps belong to the release process, not the skill.
- Place the bullet under the right
### Added | Changed | Fixed | Removed subsection.
7. Regenerate the in-app JSON
npm run updates
This rewrites src/routes/[[locale]]/updates/updates.json from the changelog. The Svelte page picks the new entry up automatically.
8. Verify
Per CLAUDE.md guidance:
npm run check:now
npm test
Both must pass. Show the user:
- The new bullet text (rendered, including any link target).
- Files modified (CHANGELOG.md and updates.json).
Do not commit. Leave the working tree dirty for the user to review.
Notes
- Paths in markdown link syntax are passed through to Wordplay markup unchanged — be conservative with the URLs you generate. Stick to
https://wordplay.dev/<route> from the table above unless the user provides a specific URL.
- Emoji prefix must be a single extended-pictographic grapheme (including VS16 / ZWJ sequences) followed by a space. The parser will not detect it otherwise.
- Plain bullets (no emoji prefix) still parse correctly, but should not be written by this skill — visual consistency across the page is the whole point. Older legacy entries (pre-0.17.7) remain plain.
