cs-libdoc

Generates API references from source code for libraries and frameworks.

1.1k|82|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-libdoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cs-libdoc
Source: https://github.com/liuzhengdongfortest/CodeStable/tree/main/cs-libdoc
Command: npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-libdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

libdoc generates a reference for each public surface by reading the library's source code, ensuring accuracy and up-to-date API documentation without manual drafting.

Core Features & Use Cases

  • Generate per-entry API references directly from source code using types, signatures, and exports.
  • Maintain a centralized manifest and support batch or single-entry generation for large codebases.
  • Use case: A library adds a new function; libdoc auto-detects the new API and produces its doc entry with signature, default values, and usage notes.

Quick Start

Run the libdoc workflow on your project to generate the API reference docs from your codebase.

Frequently Asked Questions about cs-libdoc

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

FAQPage Schema
How do I generate API references directly from source code?

Generating API references from source code is done by reading the library's codebase to extract interface signatures, types, defaults, and export styles, ensuring accurate and up-to-date documentation without manual drafting.

What is the best way to keep API documentation up to date for a large library?

Keeping API documentation up to date for a large library is achieved by deriving references directly from the source code, ensuring interface signatures and exports are captured accurately whenever the codebase changes.

Can I generate documentation for a single API entry instead of the entire codebase?

Yes, you can generate documentation for a single API entry, as the workflow supports both batch and single-entry generation to accommodate large codebases and centralized manifests.

Does generating API references from source code require manual drafting of usage notes?

Generating API references from source code does not require manual drafting, because the system automatically detects new APIs and produces doc entries with signatures, default values, and usage notes directly from the code.