doc-updater

Analyze TypeScript code with ts-morph and madge to regenerate codemaps and documentation.

5|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Bamose/everything-codex-cli --skill doc-updater-bamose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-updater
Source: https://github.com/Bamose/everything-codex-cli/tree/main/skills/doc-updater
Command: npx skills add https://github.com/Bamose/everything-codex-cli --skill doc-updater-bamose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps codemaps and project documentation aligned with the actual codebase, reducing drift between architecture, docs, and implementation.

Core Features & Use Cases

  • Codemap generation from code structure to illustrate architecture and dependencies.
  • Automatic documentation updates for READMEs, guides, and docs from code changes.
  • AST-based analysis of TypeScript projects to extract exports, imports, and API details for accurate docs.

Quick Start

Run the doc-updater to refresh codemaps and project documentation across your repository.

Frequently Asked Questions about doc-updater

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

FAQPage Schema
How do I automatically update documentation when my TypeScript code changes?

To automatically update documentation when TypeScript code changes, you analyze the codebase using AST analysis and dependency graphs to extract exports and imports, then regenerate READMEs and guides to keep docs in sync with implementation.

What is a codemap and how does it help maintain a codebase?

A codemap is a generated representation of code structure illustrating architecture and dependencies. It helps maintain a codebase by reducing drift between the actual implementation and project documentation, ensuring accurate architectural visualization across the repository.

How do I generate architecture diagrams from TypeScript code?

To generate architecture diagrams from TypeScript code, you use AST analysis with ts-morph and dependency graphs with madge to extract imports and exports, producing codemaps that visualize project structure.

Does this documentation automation tool work with plain JavaScript projects?

This documentation automation tool is designed for TypeScript projects, using TypeScript AST analysis with ts-morph to extract API details. It applies across the repository to generate codemaps and update guides for TypeScript codebases specifically.

What is the best way to prevent documentation drift in a repository?

The best way to prevent documentation drift is to automatically regenerate docs and codemaps from code changes using AST analysis. This keeps READMEs, guides, and architecture documentation aligned with the actual codebase implementation continuously.