Generate a version log for the new version: $ARGUMENTS
Steps:
- Read
release.txtto get the last documented version tag (e.g.v0.7.0). - Run the following git commands to gather all changes since that tag:
git log <last-tag>..HEAD --oneline --no-mergesgit diff --stat <last-tag>..HEAD
- Analyze the output and group commits by component or theme (e.g. Bridge Service, MCP Server, Vox Agents, Civ5 DLL, Mod, Infra/Build).
- Create the directory
docs/versions/if it does not exist, then write a full structured version log todocs/versions/$ARGUMENTS.mdwith this structure:- A heading with the version and today's date
- Grouped sections by component/theme, each with bullet points describing meaningful changes
- A "File Changes" section summarizing the diff stat output
- DO NOT Update
release.txt. - After writing the file, output a succinct GitHub release note to the console. It should be:
- Raw Markdown
- A handful of bullet items grouped by feature/theme (not exhaustive)
Related skills
Docker Compose Architect
DevOps
Designs optimized Docker Compose configurations.
Claude CodeCopilotadvanced
430
156
1,651
Incident Postmortem Writer
DevOps
Writes structured and blameless incident postmortem reports.
claudeCursorWindsurfintermediate
141
43
568
Runbook Creator
DevOps
Creates clear operational runbooks for common DevOps procedures.
claudeCursorWindsurfintermediate
108
32
501