Skip to content
Back to skills

Code Wiki

ASecurity

Generate wiki docs + Mermaid diagrams for any codebase.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 14, 2026
ai-agentsgonodegitapidocumentation

Works with

  • claude code
  • cli
  • api

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 14, 2026

npx -y skills add ctaxnagomi/agent-kd-skill --skill code-wiki --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Wiki?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Wiki
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ctaxnagomi-code-wiki/badge)](https://www.skillsdirectory.com/skills/ctaxnagomi-code-wiki)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-wiki
description: "Generate wiki docs + Mermaid diagrams for any codebase."
version: 1.0.0
author: Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [documentation, mermaid, architecture, diagrams, wiki]
---

# Code Wiki

Generate a full wiki for any codebase: overview, architecture, per-module deep-dives, and Mermaid diagrams. Works on local repos, private repos, and any language.

## When to Use

- User says "document this codebase" or "generate a wiki"
- Onboarding to an unfamiliar repo
- Need architecture diagrams
- Creating reference documentation

## Procedure

### Phase 1: Scan Structure

1. Run `ls` and `find -maxdepth 3` to understand layout
2. Read README and manifest files
3. Identify 8-10 key modules to document

### Phase 2: Write Overview

1. Write `README.md` with overview and module map
2. Write `architecture.md` with system diagram
3. Create `diagrams/` folder for Mermaid files

### Phase 3: Document Modules

For each module:
1. Identify 3-5 most important files
2. Read and understand the code
3. Write module doc with responsibilities, key files, public API

### Phase 4: Generate Diagrams

1. Class diagram for key types
2. Sequence diagrams for main workflows
3. Keep diagrams under 20 nodes each

### Phase 5: Finalize

1. Write `getting-started.md`
2. Write `api.md` if applicable
3. Save state to `.codewiki-state.json`

## Output Structure

```
wiki/
├── README.md
├── architecture.md
├── getting-started.md
├── api.md
├── modules/
│   ├── module-a.md
│   └── module-b.md
└── diagrams/
    ├── class-diagram.md
    └── sequences.md
```

## Pitfalls

- Fabricating components that do not exist in the code
- Generic AI prose without specific details
- Diagrams with more than 50 nodes
- Documenting tests or generated code as product code

## Verification

- All referenced files exist
- Diagrams render correctly
- Module docs match actual code
- No fabricated functions or classes

---

## How to use?

### 1. Download
Go to the [AGENT KD SKILL gallery](https://ctaxnagomi.github.io/agent-kd-skill/) and find this skill card. Click **Download** to save the SKILL.md file.

### 2. Install
Copy the downloaded SKILL.md into your agent's skills directory:

| Agent | Path |
|-------|------|
| **Hermes** | ~/.hermes/skills/hermes/code-wiki/SKILL.md |
| **opencode** | ~/.config/opencode/skills/code-wiki/SKILL.md |
| **Claude Code** | ~/.claude/skills/code-wiki/SKILL.md |

### 3. Use
Restart your agent session. The skill will auto-load when documentation is needed.

### 4. Verify
Ask your agent to document a codebase. If it generates structured wiki with diagrams, you're all set.

Files in this skill

  • SKILL.md2.7 KB
  • assembly.json249 B
  • skill.json573 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.