repo-maintenance

Classify repository files by liveness and adaptively clean or consolidate them.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill repo-maintenance-dhruvinrsoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-maintenance
Source: https://github.com/dhruvinrsoni/agentskills-garden/tree/main/skills/90-maintenance/repo-maintenance
Command: npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill repo-maintenance-dhruvinrsoni

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill tackles the challenge of maintaining a clean and optimized code repository by systematically identifying and addressing stale, duplicate, or unnecessary files and structural issues.

Core Features & Use Cases

  • File Inventory & Classification: Maps all tracked files, categorizing them by liveness (active, dormant, dead, duplicate).
  • Value Assessment: Employs a four-question framework to determine if files should be kept, merged, activated, or archived before deletion.
  • Content Consolidation: Merges overlapping content from multiple files into a single, crisp document.
  • Structural Audits: Identifies repo-level issues like stale configurations, orphaned tests, and documentation rot.
  • Adaptive Strategy: Pivots cleanup strategy based on discovered value, prioritizing preservation and optimization over simple deletion.
  • Use Case: A large project has accumulated many old scripts and documentation files over time. This Skill can be used to identify which files are truly unused, which can be reactivated, and which contain unique value that should be preserved or consolidated, leading to a smaller, more manageable repository.

Quick Start

Use the repo-maintenance skill to perform an adaptive cleanup of the current repository, focusing on reducing file count.

Frequently Asked Questions about repo-maintenance

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

FAQPage Schema
How do I clean up a code repository with dormant and dead files?

Repository maintenance systematically inventories and classifies files by liveness, identifying active, dormant, dead, or duplicate files to decide whether they should be kept, merged, activated, archived, or deleted.

What is the best way to find and consolidate duplicate documentation in a project?

Consolidating duplicate documentation involves mapping overlapping content across multiple files and merging them into a single, crisp document, preserving unique value while reducing overall file count.

How do I audit my repository for stale configurations and orphaned tests?

Structural audits identify repository-level issues like stale configurations, orphaned tests, and documentation rot by evaluating the codebase structure and adapting the cleanup strategy based on discovered value.

Can I reactivate dormant scripts instead of deleting them during code cleanup?

Yes, code cleanup uses a four-question value assessment framework to evaluate dormant scripts before deletion, allowing you to activate, archive, merge, or keep files based on their discovered value.

When should I use an adaptive strategy for repository maintenance?

An adaptive strategy for repository maintenance is ideal when a large project has accumulated old scripts and documentation, requiring you to pivot cleanup priorities from simple deletion to preservation and structural optimization.