feat: extract CHANGELOG_WORKFLOW resolver from /ship

Move changelog generation logic into a reusable resolver. The resolver
is changelog-only (no version bump per Codex review recommendation).
Adds voice rules inline. /ship Step 5 now uses {{CHANGELOG_WORKFLOW}}.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-03-28 23:52:10 -07:00
parent 1e1188ae2a
commit cad18c785f
4 changed files with 49 additions and 42 deletions
+2 -1
View File
@@ -1714,7 +1714,7 @@ already knows. A good test: would this insight save time in a future session? If
---
## Step 5: CHANGELOG (auto-generate)
## CHANGELOG (auto-generate)
1. Read `CHANGELOG.md` header to know the format.
@@ -1747,6 +1747,7 @@ already knows. A good test: would this insight save time in a future session? If
- Write concise, descriptive bullet points
- Insert after the file header (line 5), dated today
- Format: `## [X.Y.Z.W] - YYYY-MM-DD`
- **Voice:** Lead with what the user can now **do** that they couldn't before. Use plain language, not implementation details. Never mention TODOS.md, internal tracking, or contributor-facing details.
6. **Cross-check:** Compare your CHANGELOG entry against the commit list from step 2.
Every commit must map to at least one bullet point. If any commit is unrepresented,