staleness-metrics

Measure documentation freshness against code changes and generate staleness reports.

Updated Jan 26, 2026

Search Tags:#documentation #reporting #staleness #code #thresholds #aging

Ready to run

npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill staleness-metrics

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: staleness-metrics
Source: https://github.com/l3ocho/mktpl-claude-datasaas/tree/main/plugins/doc-guardian/skills/staleness-metrics
Command: npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill staleness-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Measures documentation freshness relative to code changes to prevent documentation drift and misalignment between docs and code.

Core Features & Use Cases

Staleness Calculation: compute Commits Behind and Days Behind to gauge doc freshness.
Relationship Detection: identify direct and indirect links between docs and code modules.
Threshold-based reporting: classify freshness into Fresh, Aging, Stale, and Critical to guide actions.

Quick Start

Analyze the repository to generate a stale documentation report based on doc-age, commits behind, and code-doc relationships.

Frequently Asked Questions about staleness-metrics

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

FAQPage Schema

How do I measure documentation freshness relative to code changes?▼

Documentation freshness is measured by calculating commits behind and days behind to gauge staleness. This detects misalignment between docs and code modules by analyzing commit-based aging and direct or indirect directory relationships.

What is documentation drift and how do I detect it across a repository?▼

Documentation drift occurs when docs become outdated relative to code changes. You detect it through project-wide audits that analyze doc-age, track commits behind, and identify direct and indirect links between documentation files and code modules.

How do I generate a stale documentation report for a repository health check?▼

To generate a stale documentation report, analyze the repository to compute doc-age, commits behind, and code-doc relationships. The structured report classifies freshness into Fresh, Aging, Stale, and Critical categories using configurable thresholds.

Can I configure staleness thresholds to classify documentation freshness?▼

Yes, you can configure staleness thresholds to classify documentation freshness into Fresh, Aging, Stale, and Critical categories. This threshold-based reporting guides actions by highlighting which docs require immediate updates based on commit and age analysis.

Does this documentation staleness analysis work for project-wide directory structures?▼

Yes, documentation staleness analysis applies to project-wide doc audits and repository health checks. It implements relationship detection across directories, identifying both direct and indirect links between documentation and code modules.

What is the best way to prevent documentation drift in a codebase?▼

The best way to prevent documentation drift is implementing commit-based staleness calculation and age-based analysis. By detecting code-doc relationships and applying threshold-based reporting, you can identify and update stale documentation before it misleads users.