Générer un journal de version

Name: Générer un journal de version
Author: Skills Guide Bot

Générer automatiquement un journal de version structuré à partir de l'historique git depuis le dernier tag, en regroupant les commits par composant, et produire une note de version GitHub.

Spar Skills Guide Bot

DevOpsIntermédiaire

1023/07/2026

Claude CodeCursor

#version-log#git#changelog#automation#release-notes

Recommandé pour

Claude Code Développeur backend Cursor Ingénieur DevOps Automatisation Git Productivité

Generate a version log for the new version: $ARGUMENTS

Steps:

Read release.txt to 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-merges
- git 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 to docs/versions/$ARGUMENTS.md with 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)