fork-fleet

List active GitHub forks and compare each to upstream for divergence.

6|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/anajuliabit/aeon --skill fork-fleet-anajuliabit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fork-fleet
Source: https://github.com/anajuliabit/aeon/tree/main/skills/fork-fleet
Command: npx skills add https://github.com/anajuliabit/aeon --skill fork-fleet-anajuliabit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of keeping up with changes across an evolving set of forked repositories by automatically inventorying active forks and surfacing the specific work worth acting on.

Core Features & Use Cases

  • Weekly fork inventory with activity tiers: Classifies forks as active, stale, or dormant based on push history so you can focus where change is happening.
  • One-call per-fork divergence detection: Compares each active fork against its upstream using GitHub’s compare API to detect ahead/behind status and changed files efficiently.
  • Actionable promotion and review candidates: Identifies new or modified skill definitions and notable config/workflow/content changes, then ranks forks by a substance-weighted score.
  • Delta-aware reporting: Tracks week-over-week changes (new forks, new active forks, new skills, and went-stale events) to keep notifications meaningful.
  • Use Case: If community forks are adding new skills or improving existing ones, this skill generates a report that tells you exactly which upstream contributions to cherry-pick or review.

Quick Start

Run the fork-fleet skill on schedule to generate a weekly report of upstream contribution candidates by scanning your active Aeon fork fleet.

Frequently Asked Questions about fork-fleet

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

FAQPage Schema
How do I monitor diverged GitHub forks to promote upstream fixes?

To monitor diverged GitHub forks, you can inventory active forks and compare each against upstream using the compare API to detect ahead/behind commit drift and identify modified skill definitions worth promoting as upstream fixes.

What is fork divergence detection and how does it work?

Fork divergence detection works by comparing active forks against upstream using GitHub's compare API to measure ahead/behind commit drift, classify changed files, and generate a substance-weighted score for each fork.

How do I track week-over-week state delta changes in active forks?

You can track week-over-week state delta changes by classifying forks based on push history tiers, logging new forks, new active forks, new skills, and went-stale events to generate meaningful delta-aware reporting notifications.

Does GitHub fork monitoring require API access for cross-repo compare?

Yes, GitHub fork monitoring requires GitHub API access to retrieve the repository forking inventory and execute cross-repo compare operations for per-fork file classification and substance-weighted scoring.

What's the best way to find new skills and config changes across community forks?

The best way to find new skills and config changes is to scan active forks for new or modified skill definitions and configuration/workflow/content changes, then rank them by a substance-weighted score to surface review candidates.

Can I schedule autonomous agent fork fleet monitoring on a cron?

Yes, you can schedule autonomous agent fork fleet monitoring on a cron to generate weekly reports of upstream contribution candidates by scanning active forks, measuring commit drift, and tracking stateful week-over-week deltas.