skills.rest
BB-84C
BB-84CCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

write-release-changelog

Generate player-facing release notes from internal modpack change data.

11|3|Updated Apr 15, 2026
Search Tags:#changelog#release-notes#modpack#product-documentation#user-communication#bethesda-modding#mod-update
One-click install
npx skills add https://github.com/BB-84C/bgs-modding-superpowers --skill write-release-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-release-changelog
Source: https://github.com/BB-84C/bgs-modding-superpowers/tree/main/docs/internal/future-skills/write-release-changelog
Command: npx skills add https://github.com/BB-84C/bgs-modding-superpowers --skill write-release-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually converting internal modpack change logs into clear, player-facing release notes is time-consuming and often inconsistent, leading to confusing updates for end users.

Core Features & Use Cases

  • Automated Categorization: Groups internal changes into player-readable categories like bug fixes, new features, and breaking changes.
  • Warning Integration: Automatically adds necessary upgrade and save compatibility warnings when relevant changes are detected.
  • Use Case: For example, if you have a list of 30 internal mod updates for your Fallout 4 modpack, this skill will transform them into a structured, easy-to-read public changelog entry with all required warnings included.

Quick Start

Use the write-release-changelog skill to turn my latest internal modpack change log into a public-facing release note for the upcoming update.

Frequently Asked Questions about write-release-changelog

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

FAQPage Schema
How do I generate player-facing release notes for a Bethesda modpack update?▼

To generate player-facing release notes for a Bethesda modpack update, input your internal change data to automatically group changes into categories like bug fixes and new features while maintaining concise public-facing wording.

What is the best way to structure modpack changelogs for end users?▼

The best way to structure modpack changelogs is by grouping internal changes into player-readable categories such as new features, bug fixes, and breaking changes to ensure clear user communication.

How do I add save compatibility warnings to modpack release notes?▼

Save compatibility warnings are automatically added to modpack release notes when relevant breaking changes are detected in your internal change data, protecting players from save corruption.

Can I convert a large list of internal mod updates into a public changelog entry?▼

Yes, you can convert a large list of internal mod updates into a structured public changelog entry, transforming dozens of internal changes into an easy-to-read release note.

Does this automated release notes generation work for all Bethesda Game Studio modpacks?▼

Automated release notes generation is explicitly designed for Bethesda Game Studio modpacks, applying modding community standards to prepare public releases or release candidates.

Related Skills

Explore More Product & Management Skills→
MichaelSolatiMichaelSolati

patch-notes

Translate internal game development change records into player-facing patch notes.

Community
Advanced
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
TitoPrauseeTitoPrausee

mrpack-modpack-builder

Build Modrinth .mrpack archives from curated mod lists and publish GitHub release assets.

Community
Advanced
AztecProtocolAztecProtocol
449

updating-changelog

Generate changelog drafts by analyzing git diffs between next and HEAD.

Official
Intermediate