writing-modpack-changelog

Generate player-facing changelogs for a Bethesda modpack by drafting grouped release notes that categorize changes into Added, Changed, Fixed, and Removed buckets. This skill outputs structured markdown formatted for platforms like Nexus Mods, Discord, and GitHub releases automatically.

Format release notes from a modpack dev-log by summarizing internal entries into player-facing changelog bullets. This process requires user confirmation before inclusion to prevent leaking sensitive curator notes into the final markdown output.

Semantic versioning for modpack updates suggests major version bumps for load-order or save-breaking changes, minor bumps for new mods, and patch bumps for fixes. This categorization prevents duplicate version entries and aligns with the release impact.

Automated changelog generation supports ModDB and Nexus Mods releases by producing structured markdown with semver-aligned version headings. It formats grouped changes consistently across these platforms, eliminating manual formatting work for modpack curators.

The changelog generator omits empty change categories to reduce noise in the release notes. It organizes updates into standard buckets like Added, Changed, Fixed, Removed, and Compatibility, only including sections that contain actual changes.

The modpack changelog skill outputs a markdown file, specifically creating a `release-changelog.md` document if it does not exist. It applies the correct header structure with semver-aligned version headings and categorized change buckets for player readability.