Generate documentation pages from a package's TypeScript/JS source code.
npx skills add https://github.com/JanuaryLabs/deepagents --skill write-docs-januarylabs
Please help me install this Agent Skill. Skill: write-docs Source: https://github.com/JanuaryLabs/deepagents/tree/main/.claude/skills/write-docs Command: npx skills add https://github.com/JanuaryLabs/deepagents --skill write-docs-januarylabs
This skill automatically generates documentation for a software package by analyzing its source code, reducing manual writing time and aligning docs with the codebase.
Provide the target package name and let the skill generate docs automatically from its source.
High-intent search queries and answers about installing and using this skill.
You can auto-generate package documentation by analyzing TypeScript source code to identify public exports, then spawning parallel sub-agents to write individual feature pages and an overview. This approach parses your codebase directly to produce structured markdown documentation.
Creating per-feature documentation pages involves parsing the package's source to extract its architecture and public exports, then generating one dedicated page per feature. The system assembles these pages and updates the project's metadata file automatically.
Yes, you can automatically extract public exports and architecture for package docs. The tool analyzes the source directory to identify classes, functions, and types, using this structure to generate comprehensive getting started and feature pages.
Documentation generation works by parsing TypeScript and JavaScript source files. It reads the source directory to identify public exports and architecture, then produces an overview and individual feature pages from the analyzed code.
The best way to write markdown docs for multiple features in parallel is spawning doc-writer sub-agents. Each sub-agent generates an individual page based on the parsed source code, which are then assembled into a complete documentation set with updated metadata.
No, you do not need to manually write an overview or getting started guide. The documentation generation skill automatically creates these sections alongside per-feature pages by analyzing the package's source code and architecture.
MichealWayneCompare public API exports with documentation and test coverage across fe-tools packages.
documensoGenerate MDX documentation pages with Fumadocs components and meta.json navigation updates.
huidgeConvert a Markdown directory into a static website with a grouped sidebar.
thktGenerate Markdown API specs and OpenAPI/Swagger files from codebase analysis.
