organizar-documentacao

Audit Git changes and normalize Markdown into a Diátaxis-aligned structure.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Nomadiction8991/skills-agents-mcps --skill organizar-documentacao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organizar-documentacao
Source: https://github.com/Nomadiction8991/skills-agents-mcps/tree/main/skills/organizar-documentacao
Command: npx skills add https://github.com/Nomadiction8991/skills-agents-mcps --skill organizar-documentacao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes the target project's documentation in ./docs by applying a Diátaxis-aligned structure, leveraging Git change signals and normalizing legacy Markdown to a coherent, navigable map.

Core Features & Use Cases

  • Inspect Git to detect documentation-relevant changes and guide updates.
  • Normalize legacy Markdown into a Diátaxis-based structure with domain indexes and changelog integration.
  • Provide templates and scaffold to rapidly align new domains with the documentation map.
  • Update root index and domain pages to reflect new or moved content.

Quick Start

Run this skill against the target repository to begin auditing Git changes and reorganizing docs under ./docs.

Frequently Asked Questions about organizar-documentacao

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

FAQPage Schema
How do I organize legacy Markdown documentation into a structured format?

Organizing legacy Markdown documentation is done by normalizing files into a Diátaxis-aligned structure, creating domain indexes and changelogs to build a coherent, navigable map within the ./docs folder.

How does Git change detection work for maintaining project documentation?

Git change detection for documentation works through read-only Git inspection to identify relevant repository updates, guiding the reorganization of domain pages and root indexes to reflect new or moved content.

What is the best way to automate documentation maintenance based on Git history?

Automating documentation maintenance based on Git history involves auditing repository changes and applying templates and scaffolding to align new domains with the documentation map.

Can I use Diátaxis to restructure an existing docs folder without losing content?

Restructuring an existing docs folder with Diátaxis normalizes legacy Markdown into domain pages and updates root indexes while preserving content through a lightweight, production-grade workflow.

Does this documentation indexing approach modify my Git repository directly?

This documentation indexing approach does not modify your Git repository directly; it restricts all edits to read-only Git analysis and document normalization to safely reorganize content.

When should I not use a Diátaxis structure for my documentation?

Diátaxis should not be used when your documentation cannot be normalized into its four domain categories, as this skill enforces a lightweight, production-grade workflow strictly aligned with that specific framework.