arch-doc

Picking up an unfamiliar repository is usually a guessing game: which directory is the core module, who depends on whom, where the entry point lives, and how to actually run the thing—the answers often hide half-pages deep in a stale README or exist only in a teammate's head. arch-doc turns that into a one-line prompt. Give it a repo path and it auto-detects the project type, language, and build system, then produces a structured architecture document covering module responsibilities, internal and external dependencies (with a Mermaid diagram), entry-point identification across CLI, Web, Worker, Scheduler, and Library surfaces, and the full run cycle from install and dev to build, test, and deploy.

The output is deliberately practical: a well-scaffolded ARCHITECTURE.md generated from a consistent template, a machine-readable architecture.json for downstream tooling, and a standalone module-dependencies.mmd file you can drop straight into docs or a PR description. If no Node runtime is available it gracefully falls back to shell-based probing, so the workflow never dead-ends.

It is a good fit for developers onboarding into a new codebase, tech leads who need to backfill architecture notes, and any DSH user who wants a reliable auto-read-the-architecture step in their agent pipeline.