staleness-check

Audit repository artifacts for stale documentation, issues, branches, and structural drift.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AJB-ajb/MeshIt --skill staleness-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: staleness-check
Source: https://github.com/AJB-ajb/MeshIt/tree/main/.agents/skills/staleness-check
Command: npx skills add https://github.com/AJB-ajb/MeshIt --skill staleness-check

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill proactively identifies and helps resolve outdated documentation, neglected issues, stale branches, and structural inconsistencies within a repository, ensuring project health and maintainability.

Core Features & Use Cases

  • Stale Documentation Detection: Flags documentation that no longer accurately reflects the codebase.
  • Issue Hygiene: Identifies open issues that are resolved, outdated, or lack recent activity.
  • Branch Management: Detects merged branches that haven't been deleted and branches with no recent commits.
  • Structural Auditing: Finds empty directories, orphaned files, and configuration drift.
  • Use Case: Run this skill weekly to catch documentation mismatches before they confuse new team members, or before a release to ensure all release notes and guides are accurate.

Quick Start

Run the staleness check skill to generate a report of all stale items in the repository.

Frequently Asked Questions about staleness-check

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

FAQPage Schema
How do I find outdated documentation and stale branches in my repository?

To detect stale branches and orphaned issues, run a periodic repository health check that analyzes GitHub issues and branch activity. This skill identifies merged branches awaiting deletion and open issues lacking recent activity to maintain project currency.

What is repository staleness and how does it affect project maintainability?

Repository staleness involves outdated documentation, neglected issues, and structural inconsistencies that degrade project health. It impacts maintainability by allowing configuration drift and orphaned files to accumulate, making the codebase harder to navigate and manage.

Do I need Git and GitHub CLI installed to check for configuration drift?

Yes, Git commands and GitHub CLI access are required to perform comprehensive staleness analysis. These dependencies allow the skill to scan repository artifacts, evaluate branch status, and identify configuration drift accurately.

What's the best way to automate issue hygiene and branch cleanup?

The best way to automate issue hygiene and branch cleanup is by running a periodic repository health check weekly. This approach catches documentation mismatches, identifies resolved issues, and detects merged branches awaiting deletion before releases.

When should I run a repository structural audit for empty directories and orphaned files?

You should run a repository structural audit weekly or before a release to catch documentation mismatches early. Regular auditing identifies empty directories, orphaned files, and configuration drift, ensuring structural integrity and accurate release notes.