bifrost: Skill for Claude Code

Changelog Writer

Generate changelogs for a new Bifrost release. Reads git history to identify changes per module, asks the user for version bump type, bumps all module versions respecting the dependency hierarchy, writes transports/changelog.md and per-module changelog.md files, and updates version files.

IMPORTANT: This skill NEVER creates or modifies files under docs/. No MDX files, no docs.json updates. Only changelog.md and version files within module directories.

Module Hierarchy

Changes cascade down this dependency chain:

core → framework → plugins → transports

• core depends on nothing internal
• framework depends on core
• plugins/* each depend on core + framework
• transports depends on core + framework + all plugins

If core changes, every module below it must bump its version (at minimum a patch bump).

If framework changes (but not core), plugins and transports must bump.

If only a plugin changes, transports must bump.

If only transports changes, only transports bumps.

Usage

/changelog-writer                    # Interactive - prompts for everything
/changelog-writer <transport-ver>    # Pre-set transport version (e.g., v1.5.0)

Workflow

Step 1: Gather Current State

Read the current version of every module:

echo "core: $(cat core/version)"
echo "framework: $(cat framework/version)"
echo "transports: $(cat transports/version)"
for d in plugins/*/; do echo "$(basename $d): $(cat ${d}version)"; done

To understand the previous release state, use the latest released tags (do NOT use docs/changelogs file mtimes - that directory also holds helm-, cli-, edge-, ent-, and prerelease files):

for prefix in core framework transports; do
  git tag -l "$prefix/v*" --sort=-v:refname | head -1
done

If a docs changelog for that transport version exists (docs/changelogs/v<version>.mdx), read it to know the previous versions of all modules.

Step 2: Identify Changes Since Last Release