readme-maintainer

Audit repository folders and detect missing or stale README.md files.

1|Updated May 21, 2020
One-click install
npx skills add https://github.com/ahandsel/debugging_log --skill readme-maintainer-ahandsel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: readme-maintainer
Source: https://github.com/ahandsel/debugging_log/tree/main/skills/readme-maintainer
Command: npx skills add https://github.com/ahandsel/debugging_log --skill readme-maintainer-ahandsel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of documentation rot by ensuring that every folder in a repository contains an accurate, up-to-date README file.

Core Features & Use Cases

  • Automated Discovery: Scans the entire repository to identify folders missing documentation or containing stale information.
  • Freshness Verification: Compares existing README content against actual folder contents to flag discrepancies or broken references.
  • Use Case: Use this skill after a major refactor or project migration to automatically identify which directories need updated documentation to reflect the new file structure.

Quick Start

Run the readme-maintainer skill to audit the entire repository and generate a plan for updating missing or stale documentation files.

Frequently Asked Questions about readme-maintainer

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

FAQPage Schema
How do I audit my repository for missing or stale markdown documentation?

To audit repository documentation, you can automate directory discovery to verify README coverage and detect stale content by comparing existing files against actual tracked structures to flag discrepancies.

What is the best way to automate documentation maintenance after a major project refactor?

Automating documentation maintenance after a refactor involves scanning directories to identify folders missing accurate README files, then generating targeted update suggestions to match the new file structure.

How does automated freshness verification work for repository README files?

Freshness verification works by comparing existing README markdown content against actual directory contents to identify documentation rot, flagging discrepancies, and detecting broken file references.

Can I use an automated audit to enforce consistent documentation standards across all repository folders?

Yes, you can enforce consistent documentation standards by running an automated audit that reports on README coverage and identifies directories lacking valid markdown files across the repository.

What should I do when my repository documentation is not working due to broken references?

When repository documentation has broken references, you should audit folder structures to compare existing README content against actual directory contents, which detects discrepancies and generates targeted update suggestions.