fork-fleet

Identify and track active Aeon forks for diverged work and upstream contributions.

Updated Jun 3, 2026

Search Tags:#automation #github #metrics #skills #upstream #fork

Ready to run

npx skills add https://github.com/swarm-ai-research/aeon --skill fork-fleet-swarm-ai-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fork-fleet
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/fork-fleet
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill fork-fleet-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track and evaluate Aeon forks to identify diverged work and surface actionable upstream contribution opportunities.

Core Features & Use Cases

Automates per-fork divergence detection by comparing against the upstream and summarizing ahead/behind status
Surfaces new or modified skill implementations ready for upstream submission and collaboration
Generates a weekly digest highlighting critical changes, recommended PR targets, and risk signals for maintainers and contributors
Use Case: Maintainers monitor forks for meaningful divergence; contributors identify upstream opportunities to contribute skills to Aeon.

Quick Start

Inventory active Aeon forks and surface upstream contribution opportunities in a weekly digest.

Frequently Asked Questions about fork-fleet

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

FAQPage Schema

How do I track active GitHub forks and identify upstream contribution opportunities?▼

Tracking active GitHub forks involves comparing per-fork deltas against the upstream repository to surface diverged work. This Skill identifies new or modified skill implementations ready for upstream submission, generating a weekly digest of recommended PR targets and risk signals for maintainers.

What is the best way to detect fork divergence across managed and community repositories?▼

Detecting fork divergence requires automated per-fork comparison against upstream to summarize ahead and behind status. The Skill compares active forks weekly, scoring delta signals like new or modified skills, and optionally deep-reads selected skills to evaluate divergence.

Can I generate a weekly digest of critical changes and risk signals for my fork network?▼

Yes, you can generate a weekly digest of critical changes and risk signals for your fork network. The Skill highlights diverged work, recommended PR targets, and actionable upstream contribution opportunities, providing maintainers and contributors with automated reporting on a weekly cadence.

How does fork scoring work when comparing modified skills to the upstream baseline?▼

Fork scoring works by evaluating per-fork delta signals, such as new or modified skills and content changes, against the upstream baseline. The Skill applies automated comparison logic to these diverged metrics, producing a score that helps prioritize which forks contain ready upstream contribution candidates.

Do I need any dependencies to automate upstream contribution monitoring for Aeon forks?▼

No dependencies are required to automate upstream contribution monitoring for Aeon forks. The Skill operates independently to inventory forks and surface upstream contributors, applying weekly cadence tracking and per-fork comparison across managed and community repositories without external component requirements.

When should I use automated fork inventorying instead of manual repository comparison?▼

Automated fork inventorying should be used when tracking active Aeon forks across managed and community repositories on a weekly cadence. Manual comparison lacks the scale for per-fork delta signals, deep-reads of selected skills, and automated risk signal reporting needed to surface actionable upstream contribution opportunities effectively.