fork-fleet

Monitor code and configuration divergence between fleet forks and upstream repositories.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/enuno/noesis-aeon --skill fork-fleet-enuno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fork-fleet
Source: https://github.com/enuno/noesis-aeon/tree/main/skills/fork-fleet
Command: npx skills add https://github.com/enuno/noesis-aeon --skill fork-fleet-enuno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, python, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill identifies and reports on divergence between the fleet's active forks and the upstream repository, focusing on code and configuration differences.

Core Features & Use Cases

  • Code Divergence Monitoring: Tracks unique commits, new/modified skills, and custom schedules in active forks.
  • Config Divergence Monitoring: Compares enabled/var/model/schedule configurations against upstream defaults.
  • Use Case: Regularly monitor the fleet's health by checking for divergences in both code and configuration, enabling timely action to resolve issues.

Quick Start

Monitor fleet divergence by running the fork-fleet skill with the default scope.

Frequently Asked Questions about fork-fleet

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

FAQPage Schema
How do I monitor code divergence between active GitHub forks and the upstream repository?

To monitor code divergence between active GitHub forks and upstream, you can use this Skill to track unique commits and identify modified skills. It uses Git commands and the GitHub API for direct repository comparison.

How do I check configuration differences in fleet forks against upstream defaults?

To check configuration differences in fleet forks against upstream defaults, this Skill parses YAML files to compare enabled, model, and schedule configurations. It highlights specific deviations in your fleet's active forks.

How does fleet divergence monitoring work for custom schedules and modified skills?

Fleet divergence monitoring works by comparing active forks against the upstream repository to identify unique commits and custom schedules. It analyzes modified skills to report exact configuration and code deviations.

Do I need GitHub API permissions to track unique commits across repository forks?

Yes, you need GitHub API access with appropriate permissions to track unique commits across repository forks. The Skill requires access to both the upstream repository and the active forks to perform Git comparisons.

What is the best way to track fleet health and resolve configuration divergence?

The best way to track fleet health and resolve configuration divergence is regular monitoring of code and config differences. This Skill identifies deviations in enabled settings and custom schedules, enabling timely resolution.

What dependencies are required for comparing code and YAML configurations across forks?

Comparing code and YAML configurations across forks requires gh, jq, and python dependencies. These tools enable GitHub API access, JSON parsing, and YAML configuration analysis for comprehensive divergence monitoring.