wiki

Generate interconnected markdown wiki pages from codebase surveys and upload via droid wiki-upload.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/oElberte/dotfiles --skill wiki-oelberte
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki
Source: https://github.com/oElberte/dotfiles/tree/main/private_dot_factory/plugins/marketplaces/factory-plugins/plugins/droid-evolved/skills/wiki
Command: npx skills add https://github.com/oElberte/dotfiles --skill wiki-oelberte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an unfamiliar repository into a structured, navigable wiki so teams can understand architecture, subsystems, and how parts of the codebase work together without manually reading everything.

Core Features & Use Cases

  • Two-pass codebase survey: performs a structural scan (README/config/entry points/CI/build/lint) and then a deep code scan (flags, routes/endpoints, feature directories, services/workers) to discover complete topics.
  • Exhaustive subsystem discovery & coverage planning: produces tiered documentation pages (core vs specialized vs niche) based on the repository’s actual structure.
  • Wiki generation for Factory: outputs an interconnected set of markdown pages into a droid-wiki/ directory and uploads it via droid wiki-upload for viewing in the Factory app.

Quick Start

Ask the AI to generate the wiki for your target repository and upload it to Factory so you can browse the results in the app.

Frequently Asked Questions about wiki

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

FAQPage Schema
How do I generate codebase documentation for an unfamiliar repository?▼

To generate codebase documentation, perform a structural scan of the repository's README, config, and entry points, then execute a deep code scan for features and routes to produce an interconnected markdown wiki.

What is the best way to automate developer onboarding for a complex codebase?▼

Automating developer onboarding requires generating comprehensive wiki documentation that surveys the repository structurally and deep-scans for subsystems, providing product-level understanding without manual code reading.

Can I generate architecture documentation for evolving codebases automatically?▼

Yes, you can generate architecture documentation for evolving codebases by performing a two-pass survey that identifies tiered documentation pages based on the repository's actual structural and feature directories.

How does repository analysis work for wiki generation?▼

Repository analysis for wiki generation works by first scanning structural elements like CI, build, and lint configurations, then deep-scanning for flags, endpoints, and services to discover exhaustive subsystem topics.

What coverage rules are required for generated codebase wiki pages?▼

Generated codebase wiki pages must meet specific coverage rules, including overview, by-the-numbers, lore, contribution guide, reference sections, and optional conditional sections, all organized into a droid-wiki directory.

Does wiki generation work with repositories that have niche or specialized subsystems?▼

Wiki generation works with repositories containing specialized or niche subsystems by producing tiered documentation pages that differentiate core components from specialized features during the exhaustive subsystem discovery phase.