S StackScriber
An automatic scribe for code

Read any codebase like a paper.

StackScriber reads your repository and produces a visual map of how it actually works, alongside a generated wiki — for any TypeScript, Python, or Go codebase.

How it works

From upload to understanding in three steps.

Connect your repo or upload an archive. StackScriber parses it with real syntax trees — not pattern matching — then asks a language model to make sense of what's there.

Connect or upload

Point us at a GitHub or Azure DevOps repo, or drop a zip. We pull the source, never any secrets.

Parse and analyze

Tree-sitter extracts the call graph; embeddings and Claude cluster modules into meaningful subsystems.

Read your stack

You get a navigable diagram and a generated wiki — diff-friendly, regenerated on every push.

What you get

A documentation surface that keeps up with the code.

A real flow diagram

Not a hand-drawn sketch — a navigable, interactive graph derived from your actual imports and call sites.

A generated wiki

Top-level overview, per-cluster pages, and a file index — written by a language model that's seen your whole repo.

Always current

Webhooks trigger a fresh analysis on every push. Compare runs to see what shifted, structurally.

Polyglot, where it counts

TypeScript, JavaScript, Python, and Go on day one — covering web frontends, API services, and infra code in one place.

Languages today
TypeScript JavaScript Python Go Rust — soon Java — soon
Early access

Be among the first to try StackScriber.

We're rolling out access in waves. Drop your email and we'll let you know when your slot opens up.

// no marketing emails. Just a notification when you're in.