release-notes-slack

Convert raw Lumen GitHub release dumps into a standardized Slack announcement draft.

23|5|Updated Apr 3, 2025
One-click install
npx skills add https://github.com/LedgerHQ/lumen --skill release-notes-slack-ledgerhq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes-slack
Source: https://github.com/LedgerHQ/lumen/tree/main/.claude/skills/release-notes-slack
Command: npx skills add https://github.com/LedgerHQ/lumen --skill release-notes-slack-ledgerhq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Lumen ships coordinated releases across many @ledgerhq/lumen-* packages, so the GitHub Releases page repeats the same changes under every package. Manually condensing that into one consistent Slack announcement is tedious and error-prone, especially when breaking changes hide inside ordinary patch bumps. ## Core Features & Use Cases - De-duplicated change list: Collapses the same change echoed across multiple package blocks into a single bullet, while keeping unrelated changes that share a PR number as separate lines. - Breaking change detection: Scans commit subjects for ! markers, BREAKING CHANGE: blocks, and removed exports instead of trusting version numbers, since Lumen always ships patch bumps. - Fixed Slack format: Produces one standard Markdown message (packages updated, changes, breaking changes) and drafts it to the #lumen-releases channel via the Slack connector without sending. - Use Case: Paste a dump of the LedgerHQ/lumen Releases page covering six updated packages and receive a single ready-to-review Slack draft with alphabetized package versions, seven de-duplicated change bullets, and any breaking changes called out with migration guidance. ## Quick Start Paste the raw Lumen GitHub Releases page content and ask to format these Lumen releases as a Slack announcement for the releases channel.

Frequently Asked Questions about release-notes-slack

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

FAQPage Schema
How do I format GitHub release notes for a Slack announcement?▼

Paste the raw Releases page dump and the skill condenses it into one fixed-format Markdown message: a packages-updated list, a de-duplicated changes list with PR links, and a breaking changes section. It then drafts the message to the #lumen-releases Slack channel for review.

How are duplicate changes across multiple packages handled?▼

Changes are de-duplicated by content, not PR number. The same change echoed under five packages appears once, while one PR carrying two unrelated changes stays as two bullets. Summaries are short noun phrases ordered by ascending PR number.

Can it detect breaking changes in patch version releases?▼

Yes. It ignores version numbers entirely and scans commit subjects for a `!` before the colon, `BREAKING CHANGE:` markers, and descriptions of removed or renamed exports. Each breaking entry states what consumers should migrate to.

Does the skill send the Slack message directly?▼

No. It uses the Slack connector's draft tool against the #lumen-releases channel and returns a draft link for human review. It only sends directly if the user explicitly asks, and falls back to a copyable code block when no Slack tool is available.

Why should the message use standard Markdown instead of Slack mrkdwn?▼

The Slack connector accepts standard Markdown and converts it itself. Pre-converting to mrkdwn causes the connector to pass raw markup through untouched, so the channel sees literal asterisks and angle brackets instead of formatting.