AELSHA™ Nehemvix
Menu
Start a free guide

How Nehemvix turns a repository into a guide

A careful reading of the whole codebase, a cost you approve, and a guide checked against the code before you see it.

How a guide is made: Read, Understand, Write, Check From left to right. Your repository link, at one commit. 1 Read: fetches the code, removes secrets and runs none of it; nothing is sent to a model yet. Then the gate: you approve the model, consent and cost. 2 Understand: each file, then folders, then the whole system. 3 Write: each section for your audiences, with real diagrams. 4 Check: looks up names, links exact lines and scores the guide. Guide ready: checked before you see it. Under Understand and Write: paused at a limit or by you? Finished work is kept and never billed twice; resume on any model. You approve the model, consent and cost Repository Your link, one commit 1 Read Fetches the code Removes secrets Runs none of it Nothing sent yet 2 Understand Each file, then folders, then the whole system 3 Write Each section for your audiences, real diagrams 4 Check Looks up names Links exact lines Scores the guide Guide ready Checked before you see it Paused at a limit or by you? Finished work is kept and never billed twice; resume on any model. How a guide is made: Read, Understand, Write, Check From top to bottom. Your repository link, at one commit. 1 Read: fetches one commit, removes secrets and runs none of the code; nothing is sent to a model yet. Then the gate: you approve the model, consent and cost. 2 Understand: each file, then folders, then the whole system. 3 Write: each section for your audiences, with real diagrams. 4 Check: looks up names, links exact lines and scores the guide. Guide ready: checked before you see it. Paused at a model limit, or by you? Finished work is kept and never billed twice; resume on any model. Repository Your link, one commit 1 Read Fetches one commit. Removes secrets. Runs none of the code. Nothing sent yet. You approve the model, consent and cost 2 Understand Each file, then folders, then the whole system. 3 Write Each section for your audiences, real diagrams. 4 Check Looks up names. Links exact lines. Scores the guide. Guide ready Checked before you see it Paused at a model limit, or by you? Finished work is kept and never billed twice; resume on any model.

Open any stage for the details.

1. Read

Fetch the code at one commit, safely.

Nehemvix fetches the repository at one exact commit, without running any of its code. It lists every file, finds the languages, entry points, manifests, README and tests, and removes secrets such as keys and passwords before anything is sent to a model. Large repositories are split into parts that fit the model, and every file is summarised once and reused.

You approve the cost

Nothing is spent until you say yes.

You see how many files will be analysed, how long it will take, and the likely, low and high cost for your model, next to your limit. Adjust the limit and go ahead, or stop there.

2. Understand

From files to folders to the whole system.

File summaries are combined into folder and system views: the architecture, components and flows that every section shares. The stages in depth, with real token counts: how AI reads a large repository.

3. Write

The guides you chose, from one analysis.

From that one analysis, Nehemvix writes the guides you chose: a beginner's guide, a senior engineer's guide and an architect's guide. Each has its own sections, such as a quick start built from the README and manifests, key concepts, architecture and data flow, module reference, setup and tests, and a glossary. Diagrams are drawn from the code's real imports.

4. Check

Checked against the code before you see it.

Every file path, function and class a guide mentions is looked up in the real code. A section with names that can't be found is rewritten once, and kept only if it improves. Anything still unverified is listed for you. Citations are resolved to exact lines and link to the analysed commit. How the checks work.

Pause and resume

Finished work is kept and never billed twice; resume on any model.

Progress is saved step by step. If the server restarts, a model limit is reached or you pause, the job resumes where it stopped, on the same model or another one. Limits and pauses · How the pipeline pauses and resumes.

Read, ask, export

Read the guide at three depths, ask questions beside it, and export it to Markdown, HTML, PDF, Word or PowerPoint, with its diagrams as draw.io files.

Engineered with AELSHA™ ASTRA

Nehemvix is built with AELSHA™ ASTRA, the framework AELSHA™ uses to take AI agents to production: every step is gated, measured and checked in code. You can watch it at work in the app while your guide is made.

More on ASTRA in Nehemvix · How Nehemvix observes itself

Try it on a repository you know

Free to use with your own model key.

Start a guide