doc-tidy

What problem does it solve?

This Skill solves the time-consuming task of manually auditing scattered, disorganized documentation across a code repository, which creates maintenance overhead and makes it hard for team members to find up-to-date project information.

Core Features & Use Cases

• Full Documentation Inventory: Collects a complete list of all documentation files across root, docs/, Assets/, config, and CI template directories using parallel subagents for speed.
• Intelligent Classification: Categorizes all docs into groups like long-term design, in-code docs, temporary artifacts, and tool config to quickly identify misplacements.
• Issue Detection: Flags common problems including root file pollution, unorganized file accumulations, duplicate docs, orphaned references to deleted modules, and missing documentation for key code modules.
• Actionable Cleanup Plan: Outputs a structured, prioritized plan with a target directory structure, specific ordered actions (delete, move, merge, fill gaps), and a list of well-organized locations that require no changes.
• Use Case: For a game development repository with docs spread across the root, Assets/ folder, and .github/ templates, use this Skill to generate a full consolidation plan in minutes without manually reviewing every file.

Quick Start

Use the doc-tidy skill to scan the current repository and output a prioritized documentation cleanup plan.