Skip to content
cccskills
FreePublished on GitHub

changelog-gen

Generate and synchronize player-facing changelog files across English, Korean, and Japanese from a Git reference range. It groups related changes, organizes featured updates and fixes, and preserves localized labels and relevant media.

OriginalShow the original description

Rewrite every `docs/*/game/changelog/{order}.stable-{semver}.md` from a ref range. Default `--limit=20`.

cataclysmbn/Cataclysm-BN1,289 stars(GitHub 1,289 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Preparing changelogs between two Git refs
  • Updating English, Korean, and Japanese release notes
  • Grouping related player-facing changes
  • Organizing screenshots and video in changelogs

Files included (1)

  • SKILL.md4.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Changelog Gen

  • One ref => start..HEAD; two refs => start..end.
  • --limit=N defaults to 20 and only caps ## Featured.
  • Use cheap subagents for crawling and choice; rank groups by reactions first, then player impact.
  • Update every language (en, ko, ja...) copy with file name {order}.stable-{semver}.md.
  • Follow the style of docs/en/game/changelog/11.stable-0.11.1.md.
  • For localized docs, look up every user-visible game term first with rg -C2 -i '<term>' lang/po/{lang}.po | head.
  • If msgstr exists, use it for game terms and user-visible labels in headings/body. Do not leave English in localized docs.
  • Translate every user-visible heading, summary label, table label, and caption in localized docs. Featured, Credits, screenshots, before, and after must be localized.
  • Keep section order, media blocks, PR grouping, and tables synced to English, but never copy English labels back into localized docs.
  • Preserve videos as <video controls src="URL" title="CAPTION"></video> immediately below the feature heading and outside image tables or <details> blocks; never render video/MP4 attachments with image Markdown and never delete valid videos solely because they are videos. Use a localized media summary label only for folded image blocks that accompany videos.
  • Do not use subagents for glossary lookup. Korean title is 안정판, not Stable.
  • Korean glossary trap: Cataclysm is 카타클리즘, never 대격변.
  • After writing every changelog file and before committing/opening/updating a PR, MUST run the reviewer subagent against the generated docs.
    • Primary agent must first gather glossary evidence directly with rg -C2 -i '<term>' lang/po/{lang}.po | head; pass that evidence to the reviewer instead of asking the reviewer to perform glossary lookup.
    • Reviewer prompt must ask for issues only, not rewrites, and must cover: meme/joke/irrelevant images, Tracy/perf graphs, buggy screenshots, valid videos deleted instead of converted to <video>, video/MP4 attachments rendered with image Markdown, too many inline images that should be under <details>, spoilers, non-player-facing items in ## Featured, wrong JSON/Lua/Bugfix section placement, significant player-facing PRs buried in catch-all sections, misplaced questlines/locations/labs/finales/mod mainlines/mutation rebalances, unsynced language sections/media/labels, missing coauthors, bot/AI authors, and localized glossary mistakes.
    • Treat reviewer output as a gate: fix every valid issue, then rerun reviewer or explicitly document why remaining findings are not applied before finalizing.
  • Group related PRs into one section and link every PR + author in <details><summary>Credits</summary>.
  • Crawl PR bodies, comments, reviews, and linked source repositories with gh api; link named external mods/projects in player-facing summaries.
  • Crawl every screenshot so the user can curate later.
  • If a featured PR has multiple screenshots, include all.
  • In ## Featured, keep media visible unless a feature group has 9 or more images; if hiding 9+ images, use one media <details> block for the whole feature group instead of one <details> block per PR.
  • Format 2+ images as a markdown table. Remove images that are too wide to read at table-column width.
  • If a PR body has before/after shots, preserve them as-is in a markdown table: | {NAME} before | {NAME} after |.
  • Refer to docs/en/game/changelog/11.stable-0.11.1.md for example.
  • Keep it terse and player-facing. No corpo phrasing, hype, filler, or adverbs (NEVER it's not just A but B)
  • Modder-only content belongs in ## JSON Modding and ## Lua Modding, not ## Featured.
  • Put every bugfix in ## Bugfixes, and all JSON/Lua modding changes in ## JSON Modding and ## Lua Modding.
  • Do not bury significant player-facing work in catch-all sections. Create/reuse focused Featured groups for questlines, locations, lab/finale changes, in-repo mod mainlines, vehicle families, mutation rebalances, companions/mounts, and other release-scale themes.
  • Keep questlines separate from generic location/lab sections unless the PR is only a map room; keep lab rooms/finales/ice lab changes together; keep military airfields/blacksites in locations; keep mutation path rebalances in mutation sections.
  • If the skill still feels wrong, stop and ask to improve the skill before writing docs.

Example command

/skill changelog-gen v0.10.0 v0.11.1 --limit=20

Before/after example

| speedway before      | speedway after      |
| -------------------- | ------------------- |
| <img src="BEFORE" /> | <img src="AFTER" /> |

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use this skill to expose Cataclysm-BN game functions and utilities to Lua. It guides you through organizing functions into libraries, registering constants and callbacks, documenting the API, and handling errors so Lua scripts can use the new bindings.

  • Expose game or map functions to Lua
  • Add constants or utility functions to a Lua library
  • Let Lua scripts register callbacks
cataclysmbn/Cataclysm-BN1.3KUpdated Oct 27, 2026

Expose complex C++ classes to Lua by adding bindings for methods, inheritance, constructors, properties, and operators. The skill also guides ownership handling and registration so Lua scripts can use the intended class interface.

  • Exposing a C++ class to Lua
  • Binding inherited class methods
  • Adding constructors and properties
cataclysmbn/Cataclysm-BN1.3KUpdated Oct 27, 2026

Add Lua bindings that let Cataclysm-BN scripts access simple C++ types, including string IDs, enums, and basic read-only classes. The skill guides documentation macros, registration in the appropriate source file, and build and in-game checks.

  • Exposing a C++ string ID to Lua
  • Registering an enum for Lua scripts
  • Making a basic read-only C++ type available to Lua
cataclysmbn/Cataclysm-BN1.3KUpdated Oct 27, 2026

deno-script

FreeSummary

Create or update Deno and TypeScript scripts for Cataclysm-BN, following the project’s conventions. Use it for command-line tools, data migrations, code or documentation generators, Git hooks, and other development utilities.

  • Creating a Deno command-line utility
  • Writing a data migration script
  • Generating code or documentation
cataclysmbn/Cataclysm-BN1.3KUpdated Oct 27, 2026

i18n-context

FreeSummary

Use this skill when the same English text needs different translations in different parts of an application. It adds gettext context at the source, updates affected PO entries, and guides validation of translations and formatting checks for the touched locale.

  • Separate translations for an ambiguous label
  • Add context to translated JSON strings
  • Update and validate affected PO entries
cataclysmbn/Cataclysm-BN1.3KUpdated Oct 27, 2026

A practical reference for adding Lua bindings to Cataclysm-BN. Look up Luna macros, usertypes, libraries, type and function patterns, documentation helpers, build steps, and common errors, with examples showing how C++ types and functions become usable from Lua.

  • Look up Luna macros for a type
  • Register C++ methods and properties for Lua
  • Troubleshoot binding or build errors
cataclysmbn/Cataclysm-BN1.3KUpdated Oct 27, 2026

See all skills by cataclysmbn

Report a problem with this skill