doc-reorganize

Reorganize Markdown documentation into category subdirectories using frontmatter.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill doc-reorganize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-reorganize
Source: https://github.com/oscardlfr/AndroidCommonDoc/tree/main/skills/doc-reorganize
Command: npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill doc-reorganize

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the reorganization of documentation into categories, enhancing structure and accessibility for users.

Core Features & Use Cases

  • Automated Reorganization: Automatically restructures documentation into category subdirectories based on frontmatter.
  • Validation and Commitment: Validates existing structure and commits changes with descriptive messages.
  • Use Case: If you have a large documentation set with scattered files, use this Skill to streamline it into a logical and navigable structure.

Quick Start

Use the doc-reorganize skill to reorganize your project's documentation with doc-reorganize.

Frequently Asked Questions about doc-reorganize

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

FAQPage Schema
How do I automatically reorganize Markdown documentation into category subdirectories?

To reorganize Markdown documentation, this Skill uses file frontmatter to sort files into category subdirectories. It validates the file structure, updates cross-references, and generates a README index using `git mv` for file movements.

How do I update cross-references when moving Markdown files to new folders?

When moving Markdown files to new folders, this Skill automatically updates cross-references using `grep`. It ensures that links remain valid and navigable after the documentation is reorganized into category subdirectories.

Can I use this to reorganize documentation files that lack frontmatter?

No, this Skill reorganizes documentation files based on their frontmatter. Markdown files must contain valid frontmatter categories to be successfully sorted into category subdirectories and have a README index generated.

Does this documentation reorganization tool generate a table of contents?

Yes, this documentation reorganization tool generates a README index. This index serves as a navigational table of contents, reflecting the newly validated category subdirectory structure and updated cross-references.

What is the best way to restructure a large set of scattered Markdown files?

The best way to restructure scattered Markdown files is using automated frontmatter categorization. This Skill validates the existing structure, commits changes with descriptive messages, and uses `git mv` to maintain version history during reorganization.

Why use git mv when reorganizing documentation into subdirectories?

Using `git mv` when reorganizing documentation preserves file history during version control. This ensures that moving Markdown files into category subdirectories and updating cross-references does not break your repository's commit tracking.