doc-freshness

Detect undocumented changes and coverage gaps across MegaETH repositories.

4|8|Updated Mar 5, 2025
One-click install
npx skills add https://github.com/megaeth-labs/documentation --skill doc-freshness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-freshness
Source: https://github.com/megaeth-labs/documentation/tree/main/.claude/skills/doc-freshness
Command: npx skills add https://github.com/megaeth-labs/documentation --skill doc-freshness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects undocumented changes and coverage gaps across MegaETH repositories.

Core Features & Use Cases

  • Aggregates recent repository changes to surface gaps in public docs.
  • Supports time-window, date, git ref, and repo-filter queries for targeted audits.
  • Produces a gap report with sources, triage status, and suggested pages.

Quick Start

Run a doc freshness sweep for the last 14 days across all tracked repos.

Frequently Asked Questions about doc-freshness

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

FAQPage Schema
How do I detect undocumented changes across MegaETH repositories after a merge?

Find documentation coverage gaps by parsing a time-window or git ref filter, collecting merged PRs across MegaETH repositories, triaging changes as doc-worthy or internal, and generating a gap report with sources and suggested target pages.

What is a doc freshness sweep and when do I need one?

A doc freshness sweep is an audit that identifies documentation coverage gaps by collecting merged PRs within a specified time-window, triaging changes, and emitting a structured gap report with suggested target pages.

Can I filter a documentation gap analysis to specific MegaETH repositories like mega-evm or mega-reth?

Yes, documentation gap analysis supports repo-filter queries to target specific tracked repositories like mega-evm, mega-reth, mega-rpc, or mega-op-contracts, alongside time-window, date, and git ref filters.

How do I audit release notes for missing changes across multiple tracked repos?

Audit release notes for missing changes by running a doc freshness sweep across tracked repos using a date or git ref filter, which collects merged PRs, triages them as doc-worthy or internal, and outputs a structured gap report with suggested pages.

What is the best way to triage merged PRs for documentation coverage gaps?

The best way to triage merged PRs for documentation coverage gaps is using an automated doc audit that parses inputs, collects merged PRs in a time-window, categorizes changes as doc-worthy or internal, and produces a structured gap report.

Does the doc freshness sweep work with specific git refs or only time-based windows?

The doc freshness sweep works with both specific git refs and time-based windows, accepting time-window, date, git ref, or repo filter inputs to collect and triage merged PRs across tracked MegaETH repositories.