Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Add Telegram and Slack delivery support; update description to reflect multi-platform capabilities; add Telegram/Slack config examples
What This Skill Does
Monitors one or more GitHub repositories for new releases, compares against last-seen versions, and delivers formatted summaries to configured channels. Supports priority keyword sorting to surface relevant changelog entries first. Runs on a cron schedule or on-demand.
Combines version state tracking, changelog summarization, and multi-channel delivery in one workflow so you don't need separate scripts for fetching, formatting, and posting.
When to use it
- Daily check for new releases across multiple open source tools
- Posting release notes to a team Slack channel automatically
- Tracking pre-release versions of a framework you depend on
- Getting a filtered changelog that skips CI and dependency noise
- Setting up a forum thread per release in a Discord community
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: check for new releases and post to Discord
- 1Read release-tracker.json config and release-tracker-state.json for last known versions
- 2Run gh release list for each configured repo to fetch the latest tags
- 3Compare latest tag against stored version; skip repos with no new release
- 4Fetch release body with gh release view, parse and categorize changes by priority keywords, features, breaking changes, and fixes
- 5Deliver formatted forum post to the configured Discord channel and update the version store
A new Discord forum thread titled '📦 v2.1.0' with sections for key features, breaking changes, and fixes, and the state file updated with the new version and timestamp.
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.