doc-sweep

Audit repository Markdown documentation for stale, duplicated, or orphaned files.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Thalfman/lifegroups --skill doc-sweep-thalfman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-sweep
Source: https://github.com/Thalfman/lifegroups/tree/main/.agents/skills/doc-sweep
Command: npx skills add https://github.com/Thalfman/lifegroups --skill doc-sweep-thalfman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of auditing a repository's documentation, identifying outdated, superseded, or redundant information, and providing a detailed report for review.

Core Features & Use Cases

  • Documentation Audit: Checks the consistency and currency of all documentation in a repository.
  • Staleness Detection: Identifies stale, superseded, duplicated, contradicted, and orphaned documentation.
  • Customizable Reports: Generates a detailed report with recommendations for action on each flagged item.
  • Use Case: Ideal for maintaining the integrity of technical documentation, such as API guides, developer handbooks, and project specifications.

Quick Start

Run the doc-sweep skill to audit the documentation within your repository.

Frequently Asked Questions about doc-sweep

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

FAQPage Schema
How do I automate a documentation audit for stale markdown files in my repository?▼

Automate a documentation audit by running a top-down analysis of your repository's markdown files, which flags stale, superseded, duplicated, and orphaned documents using Git metadata.

What is the best way to detect orphaned or contradicted documentation in a codebase?▼

The best way to detect orphaned or contradicted documentation is performing an automated document audit that analyzes markdown files and cross-references Git metadata to identify inconsistencies.

How does stale content detection work for technical project specifications?▼

Stale content detection works by analyzing markdown documents against repository Git metadata to identify outdated, superseded, or redundant technical project specifications automatically.

Do I need Python to run a markdown analysis for repo maintenance?▼

Yes, you need Python installed to run the markdown analysis scripts required for executing the repository maintenance and document audit processes.

Can I generate actionable reports for flagged duplicated documents?▼

Yes, you can generate detailed reports that include specific recommendations for action on each flagged item, covering duplicated, orphaned, and superseded documents.

What are the limitations of using Git metadata for document staleness detection?▼

A limitation of using Git metadata for document staleness detection is that it primarily operates on Markdown files, meaning non-markdown assets or untracked content may bypass the audit.