skills.rest
BlocUnited-LLC
BlocUnited-LLCOFFICIAL
Explore all skills by this author →
GitHub

release-notes

Create Unreleased changelog entries for Mozaiks release-impacting changes.

14|1|Updated Jan 8, 2026
Search Tags:#changelog#versioning#documentation#scaffolding#release notes#GitHub releases#CLI updates
One-click install
npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill release-notes-blocunited-llc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/BlocUnited-LLC/mozaiks/tree/main/.claude/skills/release-notes
Command: npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill release-notes-blocunited-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents Mozaiks release notes from becoming incomplete or out of date by capturing user-visible changes while work is still fresh.

Core Features & Use Cases

  • Proactive changelog maintenance: Create an Unreleased entry for changes that affect CLI behavior, generated scaffolds, runtime/workflow/module contracts, packaging/release behavior, or public install/run/build docs.
  • Consistent user-focused writing: Write concise bullets from the user's point of view under the correct section (Added, Changed, Fixed, Removed, Security).
  • Release prep alignment: Follow the checklist for moving entries into versioned sections, resetting Unreleased, verifying the version tag, and summarizing into GitHub Release notes.

Quick Start

Update the Mozaiks release notes for a release-impacting change by completing the task: "Added a new CLI flag that changes the default output format for the quickstart command."

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I maintain changelog entries for CLI behavior changes?▼

Write release notes by placing concise, user-focused bullets under the correct section header, such as Added, Changed, Fixed, Removed, or Security. This ensures the changelog consistently reflects user-visible updates from their point of view.

When should I add an unreleased changelog entry for a new feature?▼

Add an unreleased changelog entry when changes affect CLI behavior, generated app scaffolds, runtime contracts, packaging, or public installation documentation. Capturing these user-visible updates immediately prevents release notes from becoming incomplete or out of date.

How do I prepare release notes for a new version tag and GitHub release?▼

Prepare release notes by following a checklist to move Unreleased entries into versioned sections, reset the Unreleased block, verify the version tag, and summarize the changes into GitHub Release notes for final publication.

Do I need a separate documentation tool to write release notes for PyPI packaging updates?▼

No separate documentation tool is needed to write release notes for PyPI packaging updates. Described changes are processed directly into a single concise bullet and appended to the correct changelog section under Unreleased.

What is the best way to document changes to generated app scaffolds and templates?▼

The best way to document changes to generated app scaffolds and templates is to generate a single concise bullet in the correct section style. This ensures the update is accurately captured in CHANGELOG.md under the Unreleased section.

Related Skills

Explore More Product & Management Skills→
Arist12Arist12

gen-changelog

Generate changelog entries from git diffs and update CHANGELOG.md files.

Community
Intermediate
hua0512hua0512
81

release-rust-srec

Automate rust-srec release preparation with version bumps and release notes.

Community
Advanced
cyberlife-codercyberlife-coder
84

velesdb-release

Enforce SemVer compliance and publish VelesDB releases to crates.io, PyPI, and npm.

Community
Advanced
thoeltigthoeltig

managing-changelog

Create and update CHANGELOG.md files using Common Changelog or Keep a Changelog standards.

Community
Advanced