codewiki-wiki-generator

Generates Wiki documentation for code repositories using CodeWiki MCP tools.

3|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/mambo-wang/CodingHub --skill codewiki-wiki-generator-mambo-wang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codewiki-wiki-generator
Source: https://github.com/mambo-wang/CodingHub/tree/main/.qoder/skills/codewiki-wiki-generator
Command: npx skills add https://github.com/mambo-wang/CodingHub --skill codewiki-wiki-generator-mambo-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Understanding a large or unfamiliar codebase is slow and error-prone, and manually writing architecture documentation quickly becomes outdated. This Skill automates the generation of structured, module-level Wiki documentation for any code repository and keeps it synchronized through incremental updates. ## Core Features & Use Cases - Five-Phase Documentation Workflow: Analyzes the repository, clusters components into modules, generates per-module documents with Mermaid diagrams, produces a repository overview, and manages sessions. - Three-Tier Enhancement Modes: Automatically detects available MCP servers and selects deep enhancement (codebase-memory-mcp with Leiden clustering, Cypher queries, cross-service tracing), call-graph enhancement (CodeGraph), or standard CodeWiki mode. - LLM Wiki Knowledge Base: Query generated docs and archived notes with query_wiki, archive decisions and lessons with ingest_note, and check doc-code consistency with lint_wiki. - Incremental Updates: Detects changed files via git diff, maps them to affected modules, and regenerates only what changed instead of rewriting everything. - Use Case: Point the Skill at a monorepo and receive a complete Chinese-language Wiki with per-module architecture diagrams, complexity hotspots, dead-code detection, and a cross-service topology overview. ## Quick Start Generate Wiki documentation for the repository at the current path using the codewiki skill.

Frequently Asked Questions about codewiki-wiki-generator

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

FAQPage Schema
How do I generate Wiki documentation for a code repository?▼

Run the five-phase workflow: call analyze_repo with the repository path to get a session_id, cluster components into modules, generate per-module documents with Mermaid diagrams, write an overview.md, then close the session. The Skill handles tool orchestration automatically.

What MCP servers does the CodeWiki documentation workflow support?▼

It requires the CodeWiki-CN MCP server and optionally supports codebase-memory-mcp for deep enhancement (Leiden clustering, Cypher queries) or CodeGraph for call-graph analysis. The Skill auto-detects available servers and picks the best mode.

Can I update existing Wiki docs after code changes?▼

Yes. Incremental updates use git diff against the stored commit SHA to find changed files, map them to affected modules, and regenerate only those modules plus the overview. Full regeneration happens only if metadata is missing or over half the modules are affected.

Why does my CodeWiki session return session not found?▼

The CodeWiki MCP server keeps at most 10 sessions and silently evicts the least recently used one. This usually happens when sub-agents create their own sessions instead of sharing the main agent's session_id. Re-run analyze_repo to get a fresh session.

What are the limitations of Mermaid diagrams in generated docs?▼

Node IDs must use only letters and digits, labels need square brackets, and interactive syntax like click or linkStyle is forbidden. Chinese characters, spaces, and colons in node IDs cause validation failures that must be fixed with edit_doc_file.