skills.rest
thensls
thenslsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

announce-update

Generate merge-friendly release notes from Git ranges for fork adoption.

9|Updated Mar 31, 2026
Search Tags:#automation#git#documentation#update#release-notes#announce
One-click install
npx skills add https://github.com/thensls/nsls-personal-toolkit --skill announce-update
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: announce-update
Source: https://github.com/thensls/nsls-personal-toolkit/tree/main/skills/announce-update
Command: npx skills add https://github.com/thensls/nsls-personal-toolkit --skill announce-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning a batch of skill changes into a persistent, merge-friendly release note that forks can read and selectively adopt.

Core Features & Use Cases

  • Generate a versioned release doc at updates/YYYY-MM-DD-<slug>.md and update the release log at updates/README.md.
  • Append a structured summary to the commit history for downstream disclosure and adoption.
  • Provide a drafting workflow that guides forks through safe-merge and manual steps before pulling updates.

Quick Start

Run the announce-update workflow after committing changes to generate the release doc and log for forks to review.

Frequently Asked Questions about announce-update

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

FAQPage Schema
How do I automate generating release notes from a Git commit range?▼

To automate generating release notes from a Git range, run the announce-update workflow after committing changes. It drafts per-skill summaries and captures manual steps to create a versioned release doc at updates/YYYY-MM-DD-<slug>.md.

How do I create merge-friendly release notes for repository forks?▼

Creating merge-friendly release notes for forks involves appending a structured summary to your commit history. This Skill generates persistent release documents that include opt-out guidance for forks to review before pulling updates.

What is the best way to track skill changes for downstream disclosure?▼

The best way to track skill changes for downstream disclosure is to append a structured summary to the release log at updates/README.md. This provides a persistent, merge-friendly record that forks can selectively adopt.

Does this release notes generator require any external dependencies?▼

No external dependencies are required to use this release notes generator. It operates independently across a Git range to enforce prerequisites, draft summaries, and prepare release log entries for posting.

Can I manually review and edit generated release notes before posting?▼

Yes, you can manually review generated release notes before posting. The drafting workflow guides you through safe-merge prerequisites and captures manual steps, allowing you to edit the updates/YYYY-MM-DD-<slug>.md file prior to release.

Related Skills

Explore More Content & Communication Skills→
jhlee0409jhlee0409
7

afc:release-notes

Generate categorized release notes from git commits and pull requests.

Community
Advanced
ChazzCoinChazzCoin

release-add

Append TASK-NNN or HOTFIX-NNN entries to the top release entry in tasks/RELEASES.md.

Community
Advanced
DoezerDoezer
538

release-notes

Generate markdown release notes from git commit history.

Community
Intermediate
adampieadampie

add-tool

Analyze GitHub issues and generate Nix expressions for telemetry opt-out tools.

Community
Intermediate