terminal-changelog
Terminal Changelog
Add user-facing changelog entries as terminal documents in data/worlds/mansion.rec.
Workflow
-
Find the latest terminal document with a commit reference
grep -n "update as of" data/worlds/mansion.recExtract the commit hash from the most recent entry.
-
Fetch origin/master and get commits since that reference
git fetch origin master git log <commit>..origin/master --oneline --reverse -
Analyze feature commits - Skip dependabot/CI bumps. For significant commits:
git show <hash> --stat --format="%B" | head -50 -
Write the terminal document following the format below
-
Validate
just entities
Terminal Document Format
Id: terminal_inbox_<topic>
Name: INBOX - <Subject Line>
Prototype: terminal_document
Room: office
Container: office_terminal
DescriptionLong: ```
+ FROM: frizzle@mudd.local
+ TO: team@mudd.local
+ SUBJECT: <Subject Line>
+ DATE: <YYYY-MM-DD>
+ ----------------------------------------
+
+ (update as of <full-commit-hash>)
+
+ <Body content - each line starts with "+ ">
+
+ -Frizzle
+ ```
Insert after the previous terminal_inbox entry, before # Gallery entities.
Content Guidelines
Focus on user-facing changes:
- New commands (
/pay,/use, etc.) - New items players can find or interact with
- New locations or entities
- Changes to game mechanics
Include gameplay tips:
- Where to find new things ("Check the lounge for the slot machine")
- How to use new features ("Use /pay to send money to nearby players")
- Fun interactions ("Pull the handle to win prizes!")
Tone: Casual dev update from Frizzle. Excited about new features, hints at what's coming.
Skip: Internal refactors, CI updates, dependency bumps, bug fixes unless player-visible.
More from frizzle-chan/mudd
discord-markdown
>-
31ruff-formatter
>-
30discord-py
Build Discord bots using discord.py. Use when the user asks about Discord bot development, discord.py library, bot commands, slash commands, Discord intents, or Discord API integration. Covers Client, Bot, events, commands extension, app_commands, views, buttons, modals, and cogs.
20postgres-migrations
Write safe PostgreSQL migrations that avoid blocking reads/writes. Use when creating migrations, adding columns, indexes, constraints, or modifying tables. Based on Squawk linter rules.
20healtests
Iteratively fix test failures until all tests pass. Use when tests are failing and you want Claude to automatically plan and fix them in a loop.
17add-check
Add a new code quality check to CI, justfile, and pre-commit hooks. Use when adding linters, formatters, type checkers, or other code quality tools to the project.
17