doc-tidy

Scan repositories to inventory and classify scattered documentation files.

10|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/tykisgod/quick-question --skill doc-tidy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-tidy
Source: https://github.com/tykisgod/quick-question/tree/main/skills/doc-tidy
Command: npx skills add https://github.com/tykisgod/quick-question --skill doc-tidy

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about doc-tidy

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

FAQPage Schema
How do I audit scattered documentation files in a code repository?

Documentation cleanup involves scanning your code repository to inventory scattered files across root and config directories, identifying duplicates and stale references, and outputting a prioritized action plan for moving, merging, or deleting files to achieve a target directory structure.

What is the best way to organize docs spread across root directories and CI templates?

The best way to organize scattered docs is to classify files into groups like long-term design or temporary artifacts, detect misplaced files in root or CI template locations, and generate a structured cleanup plan with specific ordered actions for consolidation.

Does the documentation cleanup plan automatically delete or move files in my repo?

No, the documentation cleanup plan does not automatically delete or move files. It outputs a prioritized list of specific actions and a target directory structure, flagging missing or stale documentation without executing any actual changes to your repository.

Can I use a doc audit tool for a game development repository with docs in the Assets folder?

Yes, you can audit a game development repository by scanning documentation spread across the root directory, Assets/ folder, and CI template locations. The tool categorizes these files and identifies misplacements to output a full consolidation plan.

What types of documentation issues are detected during a repository cleanup scan?

A repository cleanup scan detects issues such as root file pollution, unorganized file accumulations, duplicate docs, orphaned references to deleted modules, and missing documentation for key code modules, providing specific actions to resolve each problem.