Source: https://seerepo.com/docs/v0
Markdown source: https://seerepo.com/docs/v0.md
Description: Get your v0 project on GitHub, connect it to SeeRepo, and hand v0 a prompt from Health.

# See your v0 project as a map

v0, by Vercel, builds your app through prompts. Since you don't write the code yourself, SeeRepo shows you what v0 built and how its parts connect.

## Step 1: Get your v0 project on GitHub

In v0, open your project's **...** menu → **Settings** → **GitHub** → **Connect**, choose the **Git Scope** and the **Repository Name**, and click **Create Repository**: v0 creates a private repo and pushes your code. It works on a branch of its own, and **Pull Changes** brings in commits from the base branch ([v0 and GitHub](https://v0.app/docs/github)).

## Step 2: Connect that repo to SeeRepo

Sign in to SeeRepo with GitHub, give the SeeRepo GitHub App access to the repo v0 created, choose it under "**Which repo do you want to see?**" and click "**Draw my project**". See [Connect a repo](/docs/connect-a-repo).

SeeRepo recognizes a commit as v0's when its author or its Co-Authored-By line says `v0` or `v0.dev`. v0 doesn't document the author of its commits.

## Step 3: Copy a prompt from Health into v0's chat

Open **Health** in SeeRepo, tap a task and, in its sheet, click "**Copy prompt**". Here is a real one, with example file names:

```text
In my project your-name/your-repo, no file of the product imports these files:
- src/old/Banner.tsx
- src/utils/legacyFormat.ts

Check each one (look for dynamic or convention-based uses too) and delete the ones that are really unused, with their tests. Tell me what you deleted and what you kept, and why.
```

Paste it into v0's chat. See [Health](/docs/health) for every kind of task.

## Step 4: Check the change on your map

Once v0's branch is merged into your default branch, SeeRepo reads it. To see it before that, follow v0's branch as your second branch ([Follow a second branch](/docs/connect-a-repo#follow-a-second-branch)): it gets its own map. The module it touched says when it changed. See [Where the work is happening](/docs/heat-and-recent-changes).

## Troubleshooting

Common problems:

- The repo isn't on GitHub yet: finish Step 1 first
- The SeeRepo GitHub App wasn't given access to that repo
- SeeRepo reads your default branch: v0's working branch shows up once it's merged, or on its own map if you follow it as your second branch
