fork-release-tracker

What problem does it solve?

It finds and announces the moment any active fork of a parent repository cuts a real, tagged GitHub release, so you can track ecosystem “infrastructure” signals without constant manual checking.

Core Features & Use Cases

• Weekly fork release scanning: Inspects up to 80 non-archived, non-disabled forks and checks each fork’s most recent release for the last 7 days.
• Deduped, fork-only announcements: Notifies only when a fork’s (fork, tag) pair hasn’t been announced before, and stays silent when nothing new happened.
• Actionable notifications + compact articles: Sends a one-shot notification (single or multi-release) and generates an article only when there’s new signal; otherwise it logs quietly.
• Run modes and safety guardrails: Supports a dry-run mode that updates state without sending notifications, truncates untrusted release text, and omits potentially instruction-like release notes.

Quick Start

Run the fork-release-tracker skill in scheduled automation with an empty var to infer the parent repo from the current repository’s parent relationship.