changeloglisted

# Changelog — Changelog & Release Notes ## Activate When - User invokes `/godmode:changelog` - User says "update changelog", "write release notes", "what changed?" - User says "generate migration guide", "breaking change documentation" - User says "set up conventional commits", "auto-generate changelog" - Preparing a release (often chained from `/godmode:release` or `/godmode:ship`) - Recent commits introduced breaking changes that need communication - Team publishes a new version to a package registry ## Workflow ### Step 1: Analyze Change History Examine commits, PRs, and tags since the last release: ``` CHANGE ANALYSIS: Last release: <tag> (<date>) ``` Commands to gather data: ```bash # Commits since last tag git log $(git describe --tags --abbrev=0)..HEAD --oneline ``` ### Step 2: Conventional Commits Setup If not already configured, set up Conventional Commits for automatic changelog generation: #### Commit Message Format ``` <type>(<scope>)!: <description> [optional body] ``` Types: ``` CONVENTIONAL COMMIT TYPES: | Type | Description | Changelog? | ``` #### Commitlint Setup ```bash # Install commitlint npm install --save-dev @commitlint/cli @commitlint/config-conventional ``` ### Step 3: Keep a Changelog Format Generate or update CHANGELOG.md following the Keep a Changelog standard: ```markdown # Changelog This file documents all notable changes to this project. ``` #### Keep a Changelog Rules ``` CHANGELOG RULES: 1. Changelogs are for humans, not machin