ctx-blog-changelog

name	ctx-blog-changelog
description	Generate themed blog post from commits. Use when writing about changes between releases or documenting a development arc.

Generate a blog post about changes since a specific commit, with a given theme.

Before Writing

Two questions; if any answer is "no", reconsider:

1. "Is there enough change to tell a story?" → A handful of typo fixes doesn't warrant a post
2. "Is the theme clear?" → If the commit range covers unrelated work, narrow the scope or split into multiple posts

When to Use

• When documenting changes between releases
• When writing about a development arc or theme
• When the user wants to explain "what changed and why"

When NOT to Use

• For general project updates without a commit range (use /ctx-blog)
• When the changes are minor or routine maintenance
• When there's no unifying theme across the commits

Input

Required:

• Commit hash: Starting point (e.g., 040ce99, HEAD~50, v0.1.0)
• Theme: The narrative angle (e.g., "human-assisted refactoring", "the recall system")

Optional:

• Reference post: An existing post to match the style

Usage Examples

/ctx-blog-changelog 040ce99 "human-assisted refactoring"
/ctx-blog-changelog HEAD~30 "building the journal system"
/ctx-blog-changelog v0.1.0 "what's new in v0.2.0"

Process

1. Analyze the commit range:

git log --oneline <commit>..HEAD
git diff -- <commit>..HEAD
git  --format= <commit>..HEAD |  -50