code-wiki

Create and maintain a structured code wiki from a repository.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/1475505/karpathy-code-wiki-skill --skill code-wiki-1475505
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-wiki
Source: https://github.com/1475505/karpathy-code-wiki-skill/tree/main
Command: npx skills add https://github.com/1475505/karpathy-code-wiki-skill --skill code-wiki-1475505

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code repositories often lack a durable, navigable knowledge layer that remains coherent as code evolves. This skill guides IDEs/agents to transform raw source data into a structured Wiki stored under docs/wiki, while preserving the original code as the truth and enforcing a schema-driven workflow.

Core Features & Use Cases

  • Build a three-layer knowledge architecture: Raw (source code), Wiki (LLM-managed pages under docs/wiki), and Schema (AGENTS.md and schema.md) to keep governance.
  • Ingest modules to produce module pages with summaries, interfaces, dependencies, and related files; update index.md and inter-page references; log actions to log.md.
  • Support querying with linked pages, cross-references, and updated consistency; lint checks to identify contradictions and stale content; incremental updates on code changes.

Quick Start

Point the agent at your repository and run ingest to bootstrap the wiki skeleton and index structure.

Frequently Asked Questions about code-wiki

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

FAQPage Schema
How do I generate and maintain software documentation for a large codebase?

Maintain software documentation by running the ingest workflow to create a structured code wiki under docs/wiki, producing module summaries, interfaces, and dependency cross-references that update incrementally as code changes.

What is a schema-driven code wiki architecture?

A schema-driven code wiki architecture separates source code, LLM-managed wiki pages, and schema governance via AGENTS.md, ensuring documentation remains coherent, navigable, and consistent as the raw codebase evolves over time.

How to keep repository knowledge documentation consistent when code changes?

Keep knowledge documentation consistent by using lint checks to identify contradictions and stale content, applying incremental updates to wiki pages and inter-page cross-references whenever underlying source code changes.

Can I build a knowledge wiki for codebases of varying programming languages?

Yes, you can build a knowledge wiki for codebases of varying scales and programming languages, guiding the ingest, query, and lint workflows to transform raw source data into structured module pages.

What's the best way to structure code documentation for cross-referencing modules?

The best way to structure code documentation is using a three-layer architecture with Raw source, Wiki pages, and Schema, storing entries under docs/wiki and AGENTS.md to enable linked pages and cross-references.