docs-maintenance

Update Markdown files, mkdocs navigation, and internal links.

14|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill docs-maintenance-blocunited-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-maintenance
Source: https://github.com/BlocUnited-LLC/mozaiks/tree/main/.claude/skills/docs-maintenance
Command: npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill docs-maintenance-blocunited-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the risk of broken documentation by helping you make careful, repo-consistent Markdown changes that preserve working references and navigation.

Core Features & Use Cases

  • Safe documentation updates: Renames and link fixes that avoid stale paths and references.
  • Consistent doc naming: Enforces lowercase kebab-case for new Markdown files unless a different convention is required.
  • mkdocs alignment: Updates mkdocs.yml navigation and relative links when doc files move or change.
  • Prompt pack consistency: Keeps prompt packs aligned with the current repo structure and config ownership while modernizing documentation-related content.

Quick Start

Tell the AI to update your documentation task (for example, rename a Markdown file and fix the corresponding mkdocs navigation and all affected links) for the specific change you are making.

Frequently Asked Questions about docs-maintenance

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

FAQPage Schema
How do I rename a Markdown file and fix all internal links?

Mkdocs navigation updates require modifying the mkdocs.yml file to reflect any moved or renamed Markdown files. This ensures the documentation site structure stays aligned with the actual repository file paths.

How do I update mkdocs navigation when moving documentation files?

Mkdocs navigation updates require modifying the mkdocs.yml file to reflect any moved or renamed Markdown files. This ensures the documentation site structure stays aligned with the actual repository file paths.

What is the best way to maintain lowercase kebab-case naming for Markdown files?

Prompt pack modernization updates documentation-related content to align with the current repository structure. It ensures prompt configurations and ownership remain consistent while applying standardized naming conventions.

Why do documentation links break after renaming files in a repository?

Documentation maintenance limits rewrites to the explicitly requested scope to prevent unintended changes. By checking for remaining filename references, it ensures only the targeted stale links are safely corrected.

Can I modernize prompt packs without breaking documentation references?

You can modernize prompt packs without breaking documentation references by aligning the content with the current repository structure. This ensures prompt configurations remain consistent with existing config ownership and navigation.