skills.rest
razorpay
razorpayOFFICIAL
Explore all skills by this author →
Website𝕏@razorpayGitHub

write-biweekly-announcement

Generate bi-weekly Slack announcement posts from Blade changelog git diffs.

649|197|Updated Jan 28, 2020
Search Tags:#release notes#Slack#announcement#Design system#Git diff#ChangeLog#bi-weekly
One-click install
npx skills add https://github.com/razorpay/blade --skill write-biweekly-announcement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-biweekly-announcement
Source: https://github.com/razorpay/blade/tree/main/.agents/skills/write-biweekly-announcement
Command: npx skills add https://github.com/razorpay/blade --skill write-biweekly-announcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing recurring release announcements for the Blade Design System requires manually reviewing two weeks of changelog entries, categorizing changes, and formatting them into a consistent Slack-ready post, which is repetitive and error-prone.

Core Features & Use Cases

  • Automated Changelog Analysis: Uses git diff over the past two weeks on CHANGELOG.md files in the blade and blade-mcp packages to collect shipped changes.
  • Structured Announcement Format: Produces a plain-text Slack message with highlights, bug fixes, version updates, and a link to GitHub releases.
  • File Output: Writes the final announcement to an announcement.md file in the repository root for easy copy-pasting.
  • Use Case: A maintainer preparing the bi-weekly Blade update for the team Slack channel can generate a complete, consistently formatted announcement covering all versions released in the period.

Quick Start

Generate the bi-weekly Blade announcement covering the last two weeks of changelog changes.

Frequently Asked Questions about write-biweekly-announcement

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

FAQPage Schema
How do I generate a bi-weekly release announcement from a changelog?▼

Run git diff HEAD@{2.weeks.ago} HEAD -- CHANGELOG.md on the blade and blade-mcp packages, then categorize the diff entries into new features, bug fixes, and version updates. The skill formats these into a plain-text Slack announcement and saves it to announcement.md.

How to summarize git changelog changes for a Slack announcement?▼

Use the git diff command scoped to CHANGELOG.md over the desired date range, group entries by component and version in reverse chronological order, and format them as plain text without markdown since Slack messages need txt formatting.

Which packages does the Blade announcement cover?▼

The announcement covers the packages/blade and packages/blade-mcp directories only. Changelog diffs should be collected from both projects, with Blade MCP updates listed in their own section of the message.

Can I generate announcements for a period other than two weeks?▼

Yes, the git diff command accepts other ranges such as HEAD@{n.weeks.ago} to cover n weeks. Adjust the date range in the command and the announcement header to match the chosen period.

Why should the announcement avoid markdown formatting?▼

The output is intended as a Slack message, which does not render standard markdown the same way. The skill specifies plain txt formatting with emoji-style section markers so the message pastes cleanly into Slack.

Related Skills

Explore More Content & Communication Skills→
nmdranmdra
26

keep-a-changelog

Parse Git commit history and format CHANGELOG.md entries per Keep a Changelog standards.

Community
Intermediate
webrix-aiwebrix-ai
1

release-notes

Generate release notes from merged pull requests, commits, and resolved issues.

Official
Intermediate
kortix-aikortix-ai
20.2k

changelog-sync

Generates release notes from merged GitHub PRs and opens changelog pull requests.

Official
Advanced
NITRR-OfficialNITRR-Official
4

release-notes-generation

Generate GitHub release notes from conventional commit messages and Markdown files.

Official
Intermediate