Repo Revive

Revive dormant GitHub repositories by applying one targeted maintenance improvement.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill repo-revive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Repo Revive
Source: https://github.com/aaronjmars/aeon/tree/main/skills/repo-revive
Command: npx skills add https://github.com/aaronjmars/aeon --skill repo-revive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dormant GitHub repositories lose momentum when their docs, model references, and metadata go stale, making the project harder to discover and use.

Core Features & Use Cases

  • Selects a high-potential dormant repo by scoring watched repositories with stars and days of dormancy, then skips repos recently revived and ineligible repos.
  • Audits for the most visible “stale signals” such as outdated AI model references, missing Quick Start/Installation or demo assets, weak badges/metadata, and simple community issues that can be resolved with a small README clarification or tweak.
  • Creates exactly one targeted change per run (one PR) focused on maintenance rather than new features, with a fallback API update when PRs aren’t possible.
  • Drafts a revival announcement and logs the outcome so the operator can measure what was fixed and whether it improved perceived freshness.

Use case: You maintain a list of popular but inactive repos; this Skill automatically finds the best candidate and applies a single high-impact doc or metadata improvement to signal continued maintenance.

Quick Start

Use the skill to revive a dormant watched repository by letting it run on its configured schedule.

Frequently Asked Questions about Repo Revive

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

FAQPage Schema
How do I automate GitHub repository maintenance for dormant repos?

Automate GitHub repository maintenance by scoring dormant watched repositories to select a high-impact candidate, then applying one targeted fix via a pull request. This process audits outdated model references, weak metadata, and stale docs to signal continued project upkeep.

What is the best way to update outdated AI model references in README files?

The best way to update outdated AI model references in README files is to audit repository files for stale signals and submit a single targeted maintenance pull request. This refreshes doc freshness and corrects metadata without adding new features.

How do I find and fix stale documentation in inactive GitHub projects?

Find and fix stale documentation in inactive GitHub projects by auditing watched repositories via GitHub CLI for missing Quick Start guides or demo assets. The process selects one high-potential dormant repo and applies a single high-impact metadata or doc improvement.

Can I close small GitHub issues automatically to improve community engagement?

You can close small GitHub issues automatically to improve community engagement by auditing for simple user friction points. The skill resolves these with minor README clarifications or tweaks, submitting one targeted change per run.

Does this repository maintenance approach work without creating pull requests?

This repository maintenance approach works without creating pull requests by falling back to a direct API update when PRs are not possible. It ensures the targeted metadata correction or doc freshness update is still applied to the dormant repository.

How do I announce repository updates and log maintenance outcomes?

Announce repository updates and log maintenance outcomes by drafting a concise revival announcement tweet and logging the run result after the PR is created. This allows the operator to measure whether the targeted fix improved perceived project freshness.