wiki

Generate a structured Markdown wiki with architecture maps and Mermaid diagrams from a codebase.

29|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/TheWinci/mimirs --skill wiki-thewinci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki
Source: https://github.com/TheWinci/mimirs/tree/main/.claude-plugin/skills/wiki
Command: npx skills add https://github.com/TheWinci/mimirs --skill wiki-thewinci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a comprehensive, cross-linked Markdown wiki from a codebase to improve onboarding and knowledge transfer.

Core Features & Use Cases

  • Generates architecture, module, entity, and guide pages with a consistent structure.
  • Produces Mermaid diagrams and cross-links for easy navigation.
  • Keeps the wiki in sync with code changes via a manifest for incremental updates.

Quick Start

Run the wiki generator against your repository to scaffold the initial wiki.

Frequently Asked Questions about wiki

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

FAQPage Schema
How do I generate a structured wiki from my codebase automatically?

Generating a structured wiki from your codebase involves running a generator that analyzes local code semantics to produce Markdown files. It scaffolds architecture maps, module pages, and reference guides with cross-links and Mermaid diagrams for navigation.

How does semantic indexing work for codebase documentation?

Semantic indexing for codebase documentation works by locally analyzing code structure to map module relationships. It uses this index to automatically generate cross-linked Markdown pages and Mermaid diagrams reflecting the actual architecture.

Can I create Mermaid diagrams for module architecture from Markdown?

Yes, you can create Mermaid diagrams for module architecture from Markdown using an automated wiki generator. It reads the codebase structure and outputs Mermaid diagrams within Markdown pages to visualize architecture and navigation paths.

What is the best way to keep documentation in sync with code changes?

The best way to keep documentation in sync with code changes is using a manifest for incremental updates. This tracks modifications and updates the generated Markdown wiki and Mermaid diagrams without rebuilding the entire structure.

Does this wiki generator support incremental updates for large repositories?

Yes, the wiki generator supports incremental updates for large repositories using a local manifest. This allows it to process only modified files and update the existing Markdown wiki and architecture diagrams rather than regenerating everything.

Why use templated Markdown pages for codebase onboarding?

Use templated Markdown pages for codebase onboarding to ensure consistent structure across architecture, module, and entity documentation. This provides new developers with predictable, cross-linked navigation and clear reference guides.