Skip to content

The context wall ends here

You vibe-coded it.Now own it.

Geko reads your public repo and teaches it back in plain English — architecture, lessons and debug steps, all from your own files.

public repos only · 3 projects · read-only

geko — pipelineyou/your-app

$ geko analyze github.com/you/your-app

  • ingest · 68 files · node_modules skipped
  • stack · next · react · firestore · tailwind
  • architecture · 6 layers · 9 concepts
  • lessons · 8 lessons · quizzes ready

→ guidebook ready

Geko

geko“Your landing page renders from src/app/page.tsx — start there when a change goes wrong.” 🦎

sample output

Pick your depth

Three ways in.

Same repo, same voice. Pick the depth you need today.

built from your files only

Foundations

The full course, in reading order.

From “what this project actually is” to “how to ship a change without breaking three files”.

  • 6–10 lessons
  • quiz per lesson
  • 20 xp each

Debug & Learn

Describe the bug. Learn the cause.

Geko points at the files that likely cause it, gives concrete fix steps, then teaches the concept underneath.

  • 2–3 causes
  • evidence files
  • 30 xp

Architecture Overview

The map, before the lessons.

Layers, data flow and the concepts that hold it together — in plain English, built from your tree.

  • 3–7 layers
  • data flow
  • 5–12 concepts

The run

How it works

Four steps. The first two take about a minute; the analysis runs in the background while you watch.

limits, stated up front

  • Public GitHub repositories only
  • 3 projects per account during validation
  • Explains and teaches — never auto-fixes
  1. 01

    Connect a public repo

    Paste the GitHub URL. We read the tree and skip what teaches you nothing: node_modules, lockfiles, binaries, anything over 300 KB.

  2. 02

    Geko detects your stack

    Framework, database, auth, hosting — read from your manifests and folders. Deterministic, no LLM involved in this part.

  3. 03

    Pick a pathway

    Lost? Start with the map. Staying? Start with lessons. Broken? Start with debug.

  4. 04

    Prove it back

    Every lesson ends with questions answerable only from your codebase. Pass, and the XP is yours.

Geko

Ready when your repo is.

Bring a project that has grown past one file. That is where the confusion lives — and where this helps most.

Connect a repo