changelog-writer

Generate Bifrost release changelogs from git history and module dependencies.

1|Updated Mar 7, 2026

Search Tags:#automation #git #changelog #release management #versioning #bifrost

Ready to run

npx skills add https://github.com/lakshitadidwania2106/sandbox --skill changelog-writer-lakshitadidwania2106

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-writer
Source: https://github.com/lakshitadidwania2106/sandbox/tree/main/scenario_agent/bifrost/.claude/skills/changelog-writer
Command: npx skills add https://github.com/lakshitadidwania2106/sandbox --skill changelog-writer-lakshitadidwania2106

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of release changelogs for Bifrost, a complex software project, by analyzing git history and updating version files.

Core Features & Use Cases

Automated Changelog Generation: Reads git history to identify changes per module.
Version Bumping: Intelligently bumps module versions based on a defined hierarchy (core → framework → plugins → transports).
Multi-Format Changelogs: Writes both an enterprise-style changelog for transports and simple changelogs for individual modules.
Contributor Recognition: Identifies and credits external contributors based on GitHub PRs.

Quick Start

Run the changelog-writer skill with the transport version 'v1.5.0' to pre-set the transport version.

Frequently Asked Questions about changelog-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate changelog generation from git history for a multi-module project?▼

Automated changelog generation from git history analyzes commits to identify changes per module, writes enterprise-style and simple per-module changelog files, and updates version files automatically. It reads git history to identify module-specific changes and generates multi-format changelogs.

How does version bumping work for modules with strict dependency hierarchies?▼

Version bumping for strict dependency hierarchies follows a defined order: core, framework, plugins, then transports. It intelligently bumps module versions according to this hierarchy and ensures all modules receive changelog entries, even for cascading version bumps triggered by upstream changes.

Can I credit external contributors automatically when generating release notes from GitHub PRs?▼

Crediting external contributors when generating release notes from GitHub PRs is supported. The changelog generation process identifies and credits external contributors based on their GitHub pull requests, ensuring proper attribution is added directly into the final changelog files.

What is the best way to manage release versioning for the Bifrost project?▼

The best way to manage release versioning for the Bifrost project is using automated changelog generation. It analyzes git history and module dependencies, bumps versions based on the core-to-transports hierarchy, and writes both enterprise-style and per-module changelog files.

Do I need to manually specify every module version when generating a release changelog?▼

You do not need to manually specify every module version when generating a release changelog. You can run the process with a target transport version like v1.5.0, and it automatically bumps the dependent module versions following the strict core-to-transports hierarchy.

Why are changelog entries generated for modules that had no direct code changes?▼

Changelog entries are generated for unchanged modules to handle cascading version bumps. When an upstream module like core receives an update, downstream modules like plugins and transports must also bump their versions to reflect the new dependency, ensuring all modules have valid changelog entries.