release-changelog-discord-message

Generates a copy-pasteable Discord release announcement from a Todero release changelog.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/nabitllc/todero --skill release-changelog-discord-message-nabitllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog-discord-message
Source: https://github.com/nabitllc/todero/tree/main/.agents/skills/release-changelog-discord-message
Command: npx skills add https://github.com/nabitllc/todero --skill release-changelog-discord-message-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a Discord release announcement that matches the founder's voice and stays consistent with the changelog is slow and error-prone. This Skill turns an existing release changelog into a single copy-pasteable Discord post, stored as the discord_announcement document on the release issue. ## Core Features & Use Cases - Changelog-to-announcement conversion: Reads the matching releases/vYYYY.MDD.P.md changelog and reuses its version, date, highlights, and contributor list without re-deriving them. - Voice-matched template: Applies a fixed Discord template with emoji shortcodes, highlight bullets, WHATS NEXT roadmap, What's on my mind, optional Press and WHAT I NEED FROM YOU sections, and the standard closing tagline. - Issue and case integration: PUTs the announcement as the discord_announcement document on the release issue, upserts a tweet_storm child case, and posts the announcement in a fenced code block comment. - Use Case: After the release-changelog skill produces the changelog for v2026.427.0, run this Skill to draft the Discord announcement, attach it to the release issue, and hand dotta a ready-to-paste block. ## Quick Start Read the changelog for the current stable release and write the Discord announcement as the discord_announcement document on the release issue.

Frequently Asked Questions about release-changelog-discord-message

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

FAQPage Schema
How do I write a Discord release announcement from a changelog?

Read the matching releases/vYYYY.MDD.P.md changelog, then apply the announcement template: emoji-shortcode highlight bullets, WHATS NEXT roadmap, What's on my mind, Community contributors, and the closing tagline. Store the result as the discord_announcement document on the release issue.

What sections should a Discord release announcement include?

Include Highlights with one emoji shortcode per feature, a tail line linking full release notes, WHATS NEXT roadmap themes, What's on my mind, Community contributors, and the closing tagline. Press and WHAT I NEED FROM YOU sections are optional and dropped when there is no real content.

Can this skill run before the release changelog exists?

No. The skill must never run in isolation because the version, date, contributor list, and highlights must match the changelog file exactly. Run the release-changelog skill first, then generate the announcement from its output.

Does the skill post the announcement to Discord automatically?

No. It only prepares the artifact: it updates the discord_announcement document on the release issue, upserts a tweet_storm child case, and posts the announcement in a fenced code block comment for a human to copy into Discord.

Why must the announcement version match the changelog file?

The announcement is a derivative of the changelog, so mismatched versions, dates, or contributor lists create inconsistent public communication. If the changelog is updated, the announcement document must be refreshed with the latest baseRevisionId.