v4-readiness

Generate per-fork v4 upgrade readiness checklists from aeon.yml, skills.json, and MEMORY.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents v4 upgrade breakages by generating a per-fork readiness checklist that identifies which upstream-safe patterns you rely on and which v4 change vectors you must inspect before merging.

Core Features & Use Cases

  • Per-fork v4 checklist generation: Reads your fork’s configuration and catalog metadata to produce a structured Safe / Review / Custom / Action-items report for the upcoming v4 release.
  • Drift and coverage awareness: Flags missing inputs as unscanned coverage gaps so the report never silently understates risk.
  • Custom skill focus: Detects skills present on disk that are not in the upstream install fingerprint and prioritizes them for manual compatibility review.

Quick Start

Use v4-readiness to generate a readiness article for your current fork state by running it with an empty var to audit the local working tree.

Frequently Asked Questions about v4-readiness

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

FAQPage Schema
How do I check upgrade readiness for a v4 release fork?

To check v4 upgrade readiness for a fork, generate a per-fork readiness checklist by analyzing your fork’s aeon.yml, skills.json, and MEMORY.md against a v4 change manifest. This produces Safe, Review, and Custom verdicts to identify breaking interface risks before merging.

What does a v4 migration configuration audit include?

A v4 migration configuration audit includes parsing enabled skill snapshots, scanning filesystem inputs, and checking configuration schema changes. It flags missing inputs as unscanned coverage gaps and detects custom skills not present in the upstream install fingerprint for manual compatibility review.

How do I audit custom skill compatibility for a v4 migration?

Audit custom skill compatibility by detecting skills present on disk that are not in the upstream install fingerprint. The readiness checklist prioritizes these custom or MCP-adjacent skills for manual review against v4 change vectors and potential breaking interfaces.

Can I inspect remote GitHub forks for v4 upgrade risks?

Yes, you can inspect remote GitHub forks for v4 upgrade risks using optional remote fork inspection via GitHub CLI. This allows fork operators to assess upgrade readiness across stable patterns and breaking interface changes before a v4 release.

What are the limitations of automated v4 upgrade readiness checklists?

Automated v4 upgrade readiness checklists rely on parsing aeon.yml, skills.json, and MEMORY.md; missing inputs are flagged as unscanned coverage gaps so the report never silently understates risk. Custom skills outside the upstream fingerprint require manual compatibility review.