fork-release-tracker

Identify tagged releases from forks of a parent repository via the GitHub API.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/swarm-ai-research/aeon --skill fork-release-tracker-swarm-ai-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fork-release-tracker
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/fork-release-tracker
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill fork-release-tracker-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly scan — celebrate when any fork of the parent repo cuts a tagged GitHub release. Silent when no fork releases in the window.

Core Features & Use Cases

  • Identify forks with a tagged release in the last 7 days of the parent repository.
  • Generate a concise notification and a written article summarizing weekly fork activity.
  • Maintain a durable state to prevent re-announcements and cap historical entries.

Quick Start

Start the tracker to scan the parent repository and publish weekly fork-release updates.

Frequently Asked Questions about fork-release-tracker

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

FAQPage Schema
How do I automate weekly fork-release announcements for a GitHub repository?

Automate weekly fork-release announcements by using the GitHub API to fetch forks and their tagged releases, maintaining a 7-day window with durable state to publish notifications and articles. It scans the parent repository weekly and stays silent when no fork releases occur.

How does fork release monitoring work across GitHub projects?

Fork release monitoring works by fetching forks of a parent repository via the GitHub API and checking for new tagged releases within a rolling 7-day window. It maintains an LRU-announced state to prevent duplicate notifications and caps historical entries.

Do I need GitHub API credentials to track tagged releases from repository forks?

You need GitHub API access to track tagged releases from repository forks. The tracker queries the GitHub API to fetch fork data and their releases, requiring valid authentication to retrieve repository and release information.

What is the best way to prevent duplicate announcements for GitHub fork releases?

Prevent duplicate GitHub fork release announcements by maintaining a durable LRU-announced state. This state tracks previously announced releases, ensuring each tagged release generates only one notification and article summary across weekly monitoring cycles.

Why does my GitHub fork release tracker stay silent some weeks?

The GitHub fork release tracker stays silent when no forks of the parent repository cut a tagged release within the 7-day monitoring window. It only generates notifications and written articles when new tagged fork releases are detected.

How do I track new tagged releases from forks of a parent repository?

Track new tagged releases from forks of a parent repository by scanning the GitHub API weekly for fork activity. The tracker identifies forks with releases in the last 7 days and generates a concise notification and article summarizing the fork activity.