Repo Scanner

Scan GitHub repositories and generate prioritized fleet reports with taxonomy-coded opportunities.

6|2|Updated May 21, 2026

Search Tags:#github #autonomous agents #graphQL #opportunity detection #repo analysis #maintenance prioritization #stale pull requests

Ready to run

npx skills add https://github.com/anajuliabit/aeon --skill repo-scanner-anajuliabit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Repo Scanner
Source: https://github.com/anajuliabit/aeon/tree/main/skills/repo-scanner
Command: npx skills add https://github.com/anajuliabit/aeon --skill repo-scanner-anajuliabit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repo Scanner turns a GitHub org or username into a prioritized fleet report, so downstream skills can immediately act on concrete, codeable opportunities instead of vague TODOs.

Core Features & Use Cases

Bulk-scans repositories via GitHub GraphQL and derives activity categories (active, maintained, stale) based on recent pushes.
Detects stack signals and repository health gaps using a fixed taxonomy of opportunities (for example missing CI, stale PRs, missing license/dependabot, README stubs).
Produces both a fleet-level Top 5 opportunity shortlist and a detailed per-repo catalog stored in memory for downstream execution by other skills.

Quick Start

Ask the agent to run Repo Scanner for your GitHub username or org by setting the required aeon.yml var field and then let it write the prioritized catalog to memory.

Frequently Asked Questions about Repo Scanner

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

FAQPage Schema

How do I scan a GitHub org for maintenance opportunities and stale pull requests?▼

To scan a GitHub org for maintenance opportunities, you can use a repo scanner that applies GraphQL pagination to fetch repositories and derive taxonomy-coded opportunities like stale pull requests and missing CI. It outputs a prioritized catalog with a Top-5 ranking for immediate action.

What is GitHub repository health analysis and how does it detect missing CI or licensing?▼

GitHub repository health analysis evaluates your fleet's metadata and activity to detect health gaps like missing CI, missing licenses, or README stubs. It classifies repositories as active, maintained, or stale based on recent pushes and derives a fixed taxonomy of codeable opportunities.

Can I automate unattended scheduled monitoring for GitHub repo health reviews?▼

Yes, you can automate unattended scheduled monitoring workflows for GitHub repo health reviews. The scanning process evaluates repository activity, CI hygiene, and licensing checks, then writes a deterministic prioritized fleet report to memory for downstream consumers to act on autonomously.

Does the repo analysis require a GraphQL API token to extract README and metadata?▼

Yes, the repo analysis requires a GraphQL API token to perform GraphQL-based pagination for extracting README and metadata across your repositories. This ensures deterministic opportunity derivation and accurate stack signal detection for the fleet report.

What is the best way to prioritize a large GitHub fleet for stack-aware maintenance planning?▼

The best way to prioritize a large GitHub fleet for stack-aware maintenance planning is generating a Top-5 opportunity shortlist alongside a detailed per-repo catalog. This approach detects stack signals and ranks concrete codeable opportunities like missing dependabot configurations.

How do I output a prioritized GitHub repo catalog for downstream autonomous agents?▼

You output a prioritized GitHub repo catalog for downstream autonomous agents by writing the fleet report to memory in a fixed schema format. This memory output contains the Top-5 ranking and detailed per-repo taxonomy-coded opportunities for immediate downstream execution.