doc-writer

Generate markdown documentation mirroring source code directory structure.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/LayerDynamics/Lore --skill doc-writer-layerdynamics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-writer
Source: https://github.com/LayerDynamics/Lore/tree/main/lore/skills/doc-writer
Command: npx skills add https://github.com/LayerDynamics/Lore --skill doc-writer-layerdynamics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation and maintenance of code documentation, ensuring that documentation accurately reflects the source code and follows a consistent structure.

Core Features & Use Cases

  • Mirrored Structure: Documentation directories and files mirror the source code's structure.
  • Code-Only Truth: All documentation is derived strictly from reading the source code, preventing assumptions or inferences.
  • Use Case: Automatically generate API documentation for a new Python module by pointing the skill to the source code directory.

Quick Start

Use the doc-writer skill to document the code in the 'src/utils' directory.

Frequently Asked Questions about doc-writer

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

FAQPage Schema
How do I generate markdown documentation from source code automatically?

Markdown documentation is generated by scanning source files, extracting function, class, and parameter details, and writing markdown files in a mirrored directory structure. This ensures all documented elements are verifiable directly in the source code.

Can I generate API docs that mirror my existing source code directory structure?

Yes, you can generate API docs that mirror your source code directory structure. The skill creates corresponding markdown documentation files that replicate the exact hierarchy of your source directories, keeping documentation organized alongside your codebase architecture.

Does code documentation generation infer behavior from comments or strictly read source code?

Code documentation generation enforces a strict code-only truth policy, extracting information exclusively from source code content rather than inferring behavior. This ensures all documented elements remain fully verifiable within the actual source files.

What is the best way to keep API documentation synchronized with a changing codebase?

The best way to keep API documentation synchronized is to regenerate markdown files directly from source. By mirroring the directory structure and extracting information exclusively from code content, the documentation accurately reflects the current source state.

Are there limitations to generating code docs when source files lack explicit comments?

A limitation when generating code docs from sparse source files is that documentation relies strictly on verifiable code content. Because it does not infer missing context or behavior, source files lacking explicit definitions may yield minimal markdown documentation.